Today I struggled a little bit with deleting Sub-Categories. Of course I figured it out, and I was also able to mass-edit all Request who had the "old" Sub-Category asssigned.

 

However, ServiceDesk then still said, that the Sub-Category I wanted to delete is still used by "another module".

 

I switched then into the Database (MSSQL) and searched the WorkOrderStats for the affected Sub-Category ID.

 

It turned out, that we had some tickets that obviously had assigned thit Sub-Category some time ago, and at some point these requests have been merged with another request. But it looks, like in the database, the Metadata of the "old" (single) request were still assigned - hence it didn't allow me to delete the Sub-Category.

 

Is this on purpose, or an issue of the design, that once assigned Metadata to a requests stays there, even if the Request is being merged with another Request?