View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000066 | ScriptBase | Features | public | 2019-10-21 12:02 | 2019-10-21 13:43 |
| Reporter | administrator | Assigned To | richp10 | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | resolved | Resolution | fixed | ||
| Product Version | 4.15 | ||||
| Target Version | 4.15 | Fixed in Version | 4.15 | ||
| Summary | 0000066: User should be able to load script which has semaphore lock for him/herself | ||||
| Description | Under some circumstances, such as crashing out of a print run, script records can be left in a 'locked state' and show lock on the browse. Users cannot edit these records and sometimes it is necessary to run the 'remove locks' utility. It would be better if the remove locks was ONLY needed if the locks were for another user. New behaviour should be to allow user to open a record even if it is locked - as long as the lock belongs to *them*. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-10-21 12:02 | administrator | New Issue | |
| 2019-10-21 12:02 | administrator | Status | new => assigned |
| 2019-10-21 12:02 | administrator | Assigned To | => richp10 |
| 2019-10-21 13:43 | administrator | Status | assigned => resolved |
| 2019-10-21 13:43 | administrator | Resolution | open => fixed |
| 2019-10-21 13:43 | administrator | Fixed in Version | => 4.15 |
| 2019-10-21 13:43 | administrator | Note Added: 0000020 |
