View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010588 | mantisbt | bugtracker | public | 2009-06-12 09:19 | 2009-06-26 12:00 |
| Reporter | rickb | Assigned To | jreese | ||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Summary | 0010588: Rename 'assigned' state as 'approved' or 'actioned' | ||||
| Description | Mantis has a strong lifecycle design that is valuable to its success. However, the 'assigned' state suffers (mildly) from semantic confusion: there is also an 'assigned to' field. So an issue can be 'assigned' but without being 'assigned to' anybody. Or an issue can be 'assigned to' somebody without being 'assigned'. This has been confusing to my team. A simple solution would be to clarify the 'assigned' state by renaming it 'approved', 'actioned' or some similar adjective instead. This would make conversations about issues less confusing. It would also make the workflow rules clearer because the stage at which an issue is allowed to be assigned is not related to the 'assigned' state. Mantis is all about communicating information about issues so clarity is important. Hence the request to make this change. | ||||
| Tags | No tags attached. | ||||
|
You can customize the set of statuses and such in your own copy of Mantis. See the manual / admin guide [1] sections daeling with Customizing Mantis, specifically on enumerations. [2] [1] http://docs.mantisbt.org/master/en/administration_guide/c2027.html |
|