View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0024643 | mantisbt | ui | public | 2018-08-02 02:58 | 2018-09-04 01:23 |
Reporter | Mr.Bricodage | Assigned To | dregad | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Target Version | 2.17.0 | Fixed in Version | 2.17.0 | ||
Summary | 0024643: bug_actiongroup and custom bug_actiongroup don't provide the same user experience when displaying error message | ||||
Description | Errors displayed by bug_actiongroup are displayed in a table, error displayed by custom bug_actiongroup are displayed with | ||||
Steps To Reproduce | To generate an error with bug_actiongroup : just Update few bugs status to a status that is forbidden in your workflow Files are attached to show the GUI for each case. | ||||
Additional Information | bug_actiongroup.php, from row 346 to 363
bug_actiongroup_ext.php, from row 100 to 114
| ||||
Tags | No tags attached. | ||||
Attached Files | |||||
MantisBT: master d0d6b012 2018-08-02 03:29 Committer: atrol Details Diff |
Uniformize display of failed group updates Standard and custom bug group actions did not provide the same user experience when displaying error messages. bug_actiongroup.php displays errors in a table, while bug_actiongroup_ext.php prints them with <p> elements. This commit refactors the display code on both pages, by moving it to a new API function bug_group_action_print_results(). Also fixes an issue with the page footer, which was displayed behind the sidebar due to invalid HTML. Fixes 0024643, 0024644 |
Affected Issues 0024643, 0024644 |
|
mod - bug_actiongroup.php | Diff File | ||
mod - bug_actiongroup_ext.php | Diff File | ||
mod - core/bug_group_action_api.php | Diff File |