View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0014528 | mantisbt | bugtracker | public | 2012-07-30 12:24 | 2012-08-26 16:15 |
Reporter | jholladay | Assigned To | atrol | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | duplicate | ||
Summary | 0014528: Moving an issue from project with specific categories to project with global categories changes category to default | ||||
Description | As an aside, my default category happened to be 1, which I deleted long ago (not realizing that this default category was hardcoded somewhere). My system happened to crash because of that, which sucked. I had to go into the code to figure out what was happening. But that would be a different issue. Not sure if that has been reported. Heck, I'm not sure if this has been reported. | ||||
Steps To Reproduce | project A has "Category X". Project B inherits global categories and there is a global category "Category X". Default move category is "Category Y". Move issue from Project A to Project B causes category to change to "Category Y" instead of remaining "Category X" and mapping to the global category. If there is no "Category Y" then My View crashes, making it very difficult to figure out what happened, and causing a complete system outage with a "Category Not Found" error for everyone who happens to have this issue in their view. | ||||
Additional Information | I added this code to bug_move to allow it to map to a global category if the parent project didn't have the category. Not sure if this is best, but it got me around my problem.
| ||||
Tags | No tags attached. | ||||