This is an issue with all our lookup values. I wonder if we should ban deletion of entities that are referenced by issues. This is to force re-assigning these issues to alternate categories/versions/users, etc. If we do that, then issue goes away. This will also keep our database more consistent.

I think there should be 3 changes after I had to delete a project and all the categories for the project were lost and I now have 1000 issues without a category.

1. A link table between category and project so if the project is deleted the category can remain, also so there is less duplication and more consistency in the database for category names (I had a colleague add the same category in four projects with three different spellings which annoyed me greatly!).

2. A way to re-link a category to another project, perhaps a category admin page.

and

3. A way to search for orphaned issues that have category or other fields that are no longer valid.

We have dozens of large projects in a massive corporate environment with thousands of users and it really would make things easier if categories could be related and orphaned if needs be, with so much data we often cull older categories from the list but lose them in archived issues.

I'm definitely a fan of a single table of related categories so there's less inconsistency with naming and issues can move project without as many headaches.

Great work on 1.2 by the way Victor, with so many users the database was painfully slow, but now what took 30 seconds is done in 2. So quite happy with progress :)