This is something I had endless discussions about: Lukas stated the way Axon Ivy sees the states, and customers tend to have a different opinion about it. Which is also understandable.
I'd argue that the DONE state can be understood as a positive and negative end state of a task / case - the issue with DESTROYED imho is that it looks like a mistake, if this happens from a normal process flow, because it ends a case or task with a state which does not reflect that it actually was successfully worked on to a predefined end. It mixes the states up with a manual deletion, which is most likely something you'd want to filter / handle differently.
But it's deeply semantic, that's the issue here. My understanding is also contrary to the understanding Axon Ivy has, yet I can understand both ways of arguing which leaves only another path: Adjusting these states yourself.
Once a process is completed, you can simply modify the state in the System Database - we did this for a customer not liking cancelled invoices marked as destroyed. As far as I know, this should also not have any side effect on a completed case / task.
A bulk updated for these tasks / cases is probably easier than to adjust the BPMN, but remains more or less a "fix" for something a customer wants because he understands the states differently.
