View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0014013 | mantisbt | customization | public | 2012-03-07 00:38 | 2014-09-23 18:05 |
Reporter | vboctor | Assigned To | vboctor | ||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Product Version | 1.2.8 | ||||
Target Version | 1.2.10 | Fixed in Version | 1.2.10 | ||
Summary | 0014013: System notice in bug_check_workflow() | ||||
Description | I'm suspecting that this happens when there are statuses that don't exist in the workflow or vice versa. SYSTEM NOTICE Please use the "Back" button in your web browser to return to the previous page. There you can correct whatever problems were identified in this error or select another action. You can also click an option from the menu bar to go directly to a new section. Full path: C:\wamp\www\mantis\core\bug_api.php t_status_enum_workflow | ||||
Tags | No tags attached. | ||||
MantisBT: master-1.2.x ecf22ae0 2012-03-06 19:41 Details Diff |
Fixes 0014013: System notice in bug_check_workflow(). If the status workflow is defined, but there is no corresponding entry to the current state, then allow all statuses. The reasoning is that there should always be at least one possible next status. |
Affected Issues 0014013 |
|
mod - core/bug_api.php | Diff File | ||
MantisBT: master 241ae23b 2012-03-06 19:41 Details Diff |
Fixes 0014013: System notice in bug_check_workflow(). If the status workflow is defined, but there is no corresponding entry to the current state, then allow all statuses. The reasoning is that there should always be at least one possible next status. |
Affected Issues 0014013 |
|
mod - core/bug_api.php | Diff File |