Feature #12521
openTracker can not be deleted - because issues of archived projects cannot be found without unarchiving the projects
0%
Description
Redmine: 1.3.3.stable.9519 (MySQL)
MySQL: 5.0.51a-24+lenny5
ruby 1.8.7 (2010-06-23 patchlevel 299) [x86_64-linux]
rails (2.3.14, 2.3.11)
As a feature, it is not possible to delete the Trackers, of existing issues.
But even after deletion of all related issues of a tracker (in all open and archived projects), it is (sometimes) not possible to delete trackers. This is because when a project is deleted, its issues stay in the database.
A look in the Database:
- when a project is deleted of table: projects
- it's assigned issues stay in table: issues
- eg. issue 2545 has a foreign key, pointing to project 12, which was deleted
- those tickets stay around forever and can not be delete from the UI
Thus, the Tracker of issue 2545, can never be deleted, because of the "zombie" ticket.
DB-Topics: on delete cascade, referential integrity constraint
In addition, when an adminitrator trys to accesses the ticket (/issues/2545), he gets the weird message: 403 - not enough rights. Weird, because an admin has all rights. A better message would help to find bugs faster, especially if this bugs also applies to: versions, documents and so on.
By the way. Redmine is great, thx for your work.
Files