View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0006729 | mantisbt | bugtracker | public | 2006-02-19 19:42 | 2015-08-27 04:28 |
Reporter | mnrsiat | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | new | Resolution | open | ||
Product Version | 0.19.3 | ||||
Summary | 0006729: Status of ASSIGNED may exist w/o an assignee | ||||
Description |
The issue will now show the blue color meaning Assigned, but it will also show up in My View in the Unassigned area. This is, obviously, inconsistent. If you use the Assign To shortcut form on the View Issue page, both the Assign To and the Status fields get updated appropriately. | ||||
Tags | No tags attached. | ||||
Problem still exists, also in v1.1.1. Makes reporters disregard the status 'assigned' (or treat the issues as new / unassigned), as they cannot 'trust' the 'assigned'-status code. If the issue isn't assigned to anyone (or; if an assignee is removed / issue is assigned to 'none' / blank), the correct status would be 'new', right? This should be validated & status set automatically. |
|
The same also occurs when a previously assigned issue is "unassigned" (i.e. assigned to nobody). In my opinion, Mantis should not allow status Assigned with no handler. I would suggest the following behavior:
|
|
I did some dirty code hacks to change status into NEW when unassigned. Also, this request may be related: unassign when changing status to NEW 0005266 |
|