View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0012916 | mantisbt | bugtracker | public | 2011-04-07 05:02 | 2011-10-09 05:37 |
Reporter | rtlalex | Assigned To | dregad | ||
Priority | high | Severity | crash | Reproducibility | always |
Status | closed | Resolution | duplicate | ||
OS | Win 7 | OS Version | 32 bit | ||
Product Version | 1.2.5 | ||||
Summary | 0012916: Moving issues between projects causes error | ||||
Description | When moving an issue between subprojects, APPLICATION ERROR 0001502 occurs, preventing any access to the issue list. Some investigation shows that this is because the moved issue has category_id set to 1 in the bug_table and no such category exists in the category_table. The projects in question are both share the same set of categories copied from a parent project. | ||||
Steps To Reproduce | I'm not sure how much of our setup is relevant, but I'll list config and steps here: Parent project - inherits global categories, provides categories The issue occurs when moving an issue from subproject 1 to 2 (or vice-versa). Both projects appear to have an identical set of categories available. | ||||
Additional Information | As a workaround I've manually added a category into the DB with ID 1, but this means that when moving issues between projects that the category is lost. | ||||
Tags | No tags attached. | ||||