| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0012945 | mantisbt | bugtracker | public | 2011-04-18 04:50 | 2011-10-09 05:37 |
| Reporter | cor3huis | Assigned To | dregad | ||
| Priority | high | Severity | crash | Reproducibility | always |
| Status | closed | Resolution | duplicate | ||
| Product Version | 1.2.5 | ||||
| Summary | 0012945: Cannot move Issue to other Project without this category | ||||
| Description | When one moves an issue to other project a sreen displays the issue encountered APPLICATION ERROR 0001502 Category not found. 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. | ||||
| Steps To Reproduce | 1) Choose a project which has categories It happens after I moved an issue to another project. It was a Normal operation every user can do. Since I hardly use Move before I never noticed before. The issue happened possibly if the target project did not contain the category in the original project and assigned to that issue. | ||||
| Additional Information | It is quite some serious bug IMHO since mantis cannot be used after this happens, the my_view_page does not work also anymore. I temporary help gaining access to manits again by directly manipulating the Database values and delete some fields values. Do not exactly recall which from top of my head. I do not expect egular Mantis users to be able to do that. Since I could not reopen the defect (Clicked Reopen, got access denied) | ||||
| Tags | No tags attached. | ||||
 |
|
 |
Is "Inherit Global Categories" enabled in target project or not? |
|
|
Needed to delete the project in the project to make it work again, cannot re-check :(. However, I'll try to recreate the crash bug and see with whatever values I can come up. For this I need to restore a backup of the database and hope the values in there are the same. |
|
|
BTW, as expected, the back button did not help. |
 |
@atrol. I encountered this bug aswell. Inherit is turned off for the project where the issue was moved to. The project where it was in before had it turned on |
|
|
Ditto settings at my project. How best to determine the cause of defect? |
 |
Same problem here. Moved an issue and the project was secured. I had to look into the database manually to see the cause. The moved issue was assigned with category_id = 1. However, in our system this category_id did not exist anymore => error 1502 Therefore, I changed the id manually to a valid id. This made the browser work again and the user could edit the bugs again. And to avoid this to happen again, I just created a new category and changed the id manually to 1. After that, moving was not an issue. |
|
|
lwbb, to change the id of the new category is not needed. There is a configuration option $g_default_category_for_moves |
 |
Patch attached to 0013007 works for me (subprojects with inherited categories). |
 |
Based on feedback from nimmich, I assume this problem is resolved; feel free to reopen if not |
