| Tickets -> Merge better merge with more options (i.e. what to override, what not to) -
22-08-2007, 09:54 PM
Currently, the Merge function for Tickets seems to be rather unpredictable / non-intuitive. We have not been able to figure it out yet.
When merging two Tickets, it is not quite clear which Ticket properties will appear in the merged Ticket, and whether there is anyway to choose this.
For example, the usually are not able to retain our custom fields.
And we have not been able to figure out if the Ticket properties are taken from the older or from the newer Ticket (or whether some other factor is important).
I am not quite sure how you would be able to handle this better when a conflict arises, but let me know if you need inspiration from me.
_____________________
PeteV
eSupport hosted 3.11.01
|