View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004537 | mantisbt | bugtracker | public | 2004-09-14 03:10 | 2004-11-06 06:50 |
Reporter | bpfennig | Assigned To | thraxisp | ||
Priority | normal | Severity | tweak | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 0.19.0 | ||||
Fixed in Version | 0.19.1 | ||||
Summary | 0004537: "Change Status To" shows @@ sometimes | ||||
Description | If the user has the access rights to change the status but $g_status_enum_workflow is not defined for that status, the "Change Status To" popup shows @@. | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
I agree with the problem. The root cause is really an incomplete implementation of a workflow. If a status has no next statuses, it should also be unreachable. Maybe we need a workflow checker in the admin section... I can see that not changing the status should always be an option. What other status would you suggest if the workflow is undefined? |
|
I think it that case the "Change Status To" should be disabled or hidden. |
|
If the "Change Status To" is hidden, how will the bug ever get out of the bad state? |
|
Yes, you are right - then all available states should be shown. |
|
Two things need to be changed: 1) add a check in admin/check.php to validate the workflow (e.g., all states that are reachable are exitable) 2) add a default of all states in the change status dropdown if the workflow for a particular status is undefined. |
|
I attached a snap of the workflow checker. I was planning to show the access level required to reach the status as well. It lives under the Admin -> System Utilities. When the relationship graph stuff is committed, I can use the same utilities to generate this graphically. Comments are welcome. |
|
Fixed in CVS. |
|