Problem-and-incident tickets are useful when a problem or service interruption is reported by more than one person. For example, when the wireless network in an office stops working, several people might file tickets. You can treat the tickets as incident reports. Instead of handling each ticket separately, you can link the tickets to one problem ticket, and then solve the problem ticket to solve all the incident tickets.
Here's the general workflow:
- Identify a service interruption or problem that's causing people to file tickets.
- Create your own ticket to address the problem.
- Change the other tickets to incident tickets and link them to your problem ticket.
- Solve the problem ticket.
When you solve the problem ticket, the status of all the incident tickets is automatically set to solved. The comment added to the problem ticket when solved will be added to all incident tickets that are not yet closed.
Refrain from solving any of the incident tickets directly. Solving an incident ticket still leaves the other tickets unsolved. Save work by solving only the problem ticket. It automatically solves all the linked incident tickets. When the problem ticket is solved, any empty required fields on linked incident tickets are ignored and tickets are solved anyway.
To create problem-and-incident tickets
- After identifying a problem that's causing people to file tickets, create your own ticket describing the problem and set the ticket type to Problem.
- For every other ticket reporting the same problem, set the ticket type to Incident and link it to the problem ticket.
After you set the type to Incident, a second menu appears that lets you link the incident to a problem ticket.
Make sure to click Update to save the changes to the ticket.
- Solve the problem ticket.
The problem ticket has a link to a view of linked tickets so you can review the incident reports.
Solving the problem ticket solves all the incident tickets linked to it. Only the comment added when solving the problem ticket will be included in all linked incident tickets.
Tip: Use dynamic content placeholders to personalize the comment for wide distribution. Example:
For more information, see Using placeholders.
If you decide to reopen the solved problem ticket, the incident tickets aren't updated. They stay solved. If you solved a problem ticket prematurely or if you need to communicate something more to the requesters, you can easily reopen the incident tickets before solving the problem ticket again. Click the Incidents tab when viewing the problem ticket and bulk edit all of the tickets. Submit the tickets as open and proceed with re-solving the problem ticket.
Related topics
67 Comments
On linked tickets we need the ability to attach a document for the final Public comment on the incident tickets.
While the T [text] icon is visible the paperclip is not when we are selecting multiple tickets to edit linked to the Problem ticket.
Is there an APP for this?
Hi everyone,
Is it possible to reply with a dynamic content to a Problem ticket ?
Today, we're sending the message in french and english directly on the Problem ticket, so everyone receive the french & english version.
We would like to auto-adapt the answer and send only the right version to the user depending on his language.
Hey Giovanni,
Yes dynamic content will render correctly when replying to a problem ticket. This is actually a tip mentioned in our Working with problem and incident tickets article which I've linked for you :)
Let us know if you have any other questions!
Hi, Is there a way I can add all the requestors/CC list from incident(multiple) tickets to problem ticket CC list automatically when we link the incident to the problem ticket.
Also, Any possibility to link the incident to already resolved problem ticket. We have cases where the incidents are created but there is already a problem fix ticket created and released recently. Inorder to track better we need this new ticket to linked to the solved problem ticket.
Hi Adarsh,
There wouldn't be a way to automatically copy this information over from the incident ticket to the problem ticket unfortunately. However, when you post a public response to the PT and solve that ticket out, every incident ticket attached to that PT should also receive that update. That means, any CC'd users to the incident ticket should receive the update as well.
As for attaching incident tickets to a solved problem ticket, you should be able to do this already. However, you won't be able to attach an Incident ticket to a Closed problem ticket.
Let me know if you have any other questions for me :)
Thanks Brett,
Is there any trigger we can create to link the problem ticket to incident ticket automatically based on the tags.I have the child_ticket tag in the problem ticket for the incident ticket(which have a parent_ticket tag). Looking for an automated way when I create a problem ticket from the incident ticket(using linked app/project management app) it will automatically link and populate the 'Linked Problem' field with the problem just created.
Thanks
Adarsh Shet
Hi Adarsh,
I did some digging on my end and reached out to our team internally but unfortunately there's no way to automatically link an Incident ticket to a Problem ticket. This would need to be manually done by the agent.
Apologies for not being able to provide an alternative for you at this time :-/
Please sign in to leave a comment.