1 Reply Latest reply on Aug 23, 2017 6:22 AM by dcogny

    How to handle duplicate incidents from same person

    ggarcia@marchofdimes.org Apprentice

      From time to time we have users that have duplicate incidents.  This might occur if they email someone about an issue, then call the service desk - and both sources end up creating tickets. 
      The knee jerk reaction is to just close/delete an incident, but is there a cleaner way/best practice to handle this?

        • 1. Re: How to handle duplicate incidents from same person
          dcogny Expert



          In our case we "Cancel" the newest one (or the one that got less information if there is the case), and as the system ask for a reason, we refer to the one that stays open: "Cancelling Incident as duplicated, see Incident #100001"

          Also we added the option to link Incidents to Incidents, so we would link both Incidents, but that is not that necessary.


          That is our approach, but you should think what works for you, do you keep track of the time spent? maybe ask about the time when cancelling so the time spent for that analyst does not get lost, maybe "Resolve" the Incident, but add something like the previous message as resolution.


          Hope this helps!