View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0012129 | mantisbt | administration | public | 2010-07-01 12:58 | 2014-09-23 18:05 |
Reporter | KarlReichert | Assigned To | dregad | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 1.2.1 | ||||
Target Version | 1.2.11 | Fixed in Version | 1.2.11 | ||
Summary | 0012129: workflow transition to status reopened is always checked for some status on workflow transition page | ||||
Description | I'm using custom status values. However, if I now go to the "Workflow Transitions" page, the transition to "reopened" is checked from status "solved", "tested" and "closed" (please see the attachment "workflow_transitions.png"). If I do not save anything on this page and go back to the configuration report, I can see, that still everything is configured as before, i.e. the configuration is not changed. So the problem is, when opening the page "workflow transitions", MantisBT always sets transitions from the state configured to be considered as resolved to the status configured to be considered as reopened, no matter what is stored in the database. This does not break my configuration, as long as I don't save anything on page "Workflow transitions" or if I uncheck those transitions every time, before saving. But it's quite annoying and misleading. | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
I can confirm this behavior and will commit a patch later on |
|
This should now be resolved. Please download a nightly build and test, and let me know if you discover any issues with the fix. Note: in master/1.3, manage_config_workflow_page.php failed to load due to an error caused by type mismatch while calling the check_checked() function. Commit [1] fixes this. [1] https://github.com/mantisbt/mantisbt/commit/052606d21aa302142288bf5eceeaa1377ef56dac |
|
Thanks for the patch . I took over the Mantis tasks from Karl in our company and so I'm going to check this at the end of cw 16 or in cw 17. But I can't check for 1.3, because I currently don't have an 1.3 installation. I'm going to let you know, if your patch is fixing the problem for me. |
|
Thanks again, works for me on 1.2.5 and 1.2.8. As I already said, not tested on 1.3. |
|
Thanks for your testing and confirmation. And don't worry about 1.3. |
|
Hi Dregad. Maybe the same thing in 1.2.10? I still have the same problem above with other user. I'm using 1.2.10. Thanks! |
|
marco.scariot@gmail.com, the issue is marked as fixed in version 1.2.x. |
|
Ok! Thankyou very much Atrol! |
|
Marking as 'acknowledged' not resolved/closed to track that change gets ported to master-2.0.x branch |
|
MantisBT: master 7e7ba3d9 2012-04-04 04:44 Details Diff |
Fix workflow transition to status reopened always checked In manage_config_workflow_page.php, the code was always showing the 'reopened' states as checked regardless of the actual values stored in the database. This was due to storing the 'reopened' label within the array of values used to build the table to display, which consequently were always set. The code that initializes the labels has been removed from function parse_workflow(), and the logic is now handled directly in show_flag(), with globally initialized variables for better performance. Fixes 0012129 |
Affected Issues 0012129 |
|
mod - core/workflow_api.php | Diff File | ||
mod - manage_config_workflow_page.php | Diff File | ||
MantisBT: master-1.2.x 08b00de0 2012-04-04 04:44 Details Diff |
Fix workflow transition to status reopened always checked In manage_config_workflow_page.php, the code was always showing the 'reopened' states as checked regardless of the actual values stored in the database. This was due to storing the 'reopened' label within the array of values used to build the table to display, which consequently were always set. The code that initializes the labels has been removed from function parse_workflow(), and the logic is now handled directly in show_flag(), with globally initialized variables for better performance. Fixes 0012129 |
Affected Issues 0012129 |
|
mod - manage_config_workflow_page.php | Diff File | ||
MantisBT: master 052606d2 2012-04-04 05:53 Details Diff |
Fix type check error in manage_config_workflow_page.php Strict type check in function check_selected() caused an error comparing false with the status level, so replaced with 0 |
Affected Issues 0012129 |
|
mod - manage_config_workflow_page.php | Diff File |