Hi all,at my employer, we have the problem that sometimes people merge tickets wrongly.
And what happens then? Some people manage to delete the ticket links, some people manage to change the state from 'merged' to something else, but I've never seen anybody successfully split out the articles that came from the original ticket, restore the previous ticket state (or just "open" it) and delete the links correctly.
Is there already a solution to this (or possibly being worked on)? If not, I'm pondering how best to supply an undo for merges. My current thoughts: 1) introduce a transaction ID in the ticket_history table2) make sure that all individual entries in the ticket_history table that are created during a merge get the same transaction ID 3) currently a merge moves the history for each article that is merged. This would need to be changed to a copy operation, or otherwise a history entry for each article that is moved needs to be created 4) when the steps above are done, there should be enough meta data to undo a merge:
4.1) remove all LinkObjects created during a merge 4.2) move all articles back that were moved during a merge 4.3) restore the old state of the merge ticket4.4) (Optional) undo changes to dynamic fields that were done during the merge
Does that sound feasible? Did I miss anything crucial? Cheers, Moritz
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
