View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0006831 | mantisbt | customization | public | 2006-03-09 17:41 | 2010-09-19 03:13 |
Reporter | MBonner | Assigned To | dhx | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | duplicate | ||
Product Version | 1.0.1 | ||||
Summary | 0006831: Hard-Coded NEW_ constant usage | ||||
Description | the "NEW_" constant representing the status for newly submitted bugs is hard-coded in the following files. The $g_bug_submit_status constant from config_defaultsinc.php should be used instead to represent this value instead of hard-coding it. This way if someone customizes their status codes to not use "NEW" as the first value the system won't break and they won't have to hack all the PHP files where this is hard-coded. Files affected (in v1.0.1): bugupdate.php manage_config_workflow_page.php manage_config_workflowset.php bugapi.php email_api.php | ||||
Tags | No tags attached. | ||||