View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0026686 | mantisbt | bugtracker | public | 2020-02-10 07:07 | 2021-05-22 06:18 |
Reporter | bluescreenterror | Assigned To | dregad | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Target Version | 2.24.0 | Fixed in Version | 2.24.0 | ||
Summary | 0026686: Make category on bug_report_page a required field when $g_allow_no_category = OFF; | ||||
Description | When $g_allow_no_category is set to off and no category is choosen, mantis throws an error and all data from the page is lost. Is it possible to set the required property to the category field too or select a global category as default ? | ||||
Steps To Reproduce | Just try to report an Issue here and dont set a category. | ||||
Tags | No tags attached. | ||||
related to | 0022310 | closed | community | Use HTML5 "required" attribute for required form fields |
related to | 0026687 | closed | dregad | Required fields when reporting an issue, should also be when updating it |
related to | 0028618 | closed | dregad | Category empty but required does not prevent form submission on Firefox Windows and Safari |
MantisBT: master e1b5180d 2020-02-10 04:44 Details Diff |
Make Category selection list required If $g_allow_no_category is OFF, then use the HTML5 required attribute Fixes 0026686 |
Affected Issues 0026686 |
|
mod - bug_report_page.php | Diff File | ||
mod - core/print_api.php | Diff File | ||
MantisBT: master df0dc345 2020-02-10 05:04 Details Diff |
Category required in bug_actiongroup_page.php Following-up on making the field required when reporting a new issue (see issue 0026686), we can leverage the new behavior of the "(select)" OPTION by making the SELECT required to force user to select a value when performing a batch update of the category. |
Affected Issues 0026686 |
|
mod - bug_actiongroup_page.php | Diff File |