Content
View differences
Updated by Jens Ulferts over 3 years ago
When trying to delete a
* a status
* type
* role
* ... possibly others
or type, you get a generic error message that the object cannot be deleted due to being in use.
It often happens that customers complain about this because they forget they have an archived project which has these object assigned to work packages.
To improve visibility, we should:
* list where the objects are still being used and if the associated project is archived
* Optionally, allow a way to re-assign all values like for deleting work packages with an assigned time entry
* This option should also allow to force deletion if that does not lead to data corruption (e.g. if a role is deleted, all memberships need to be deleted but that would be possible).
* For roles, no overview seems to exist at all, even for non archived projects.
*
* type
* role
* ... possibly others
It often happens that customers complain about this because they forget they have an archived project which has these object assigned to work packages.
To improve visibility, we should:
* list where the objects are still being used and if the associated project is archived
* Optionally, allow a way to re-assign all values like for deleting work packages with an assigned time entry
* This option should also allow to force deletion if that does not lead to data corruption (e.g. if a role is deleted, all memberships need to be deleted but that would be possible).
* For roles, no overview seems to exist at all, even for non archived projects.