We have 3 identical incidents for which we currently have no solution. We have then created a problem and linked these 3 incidents. So far so good. But one thing bothers us, and that is that the incidents are still in the queue. Is it possible to set it so that incidents that have been linked to a problem do not appear in the queue?
I think I'd,
There may be some additional nuance in the rule needed to meet your needs, but I think this would work relatively well. If you wanted, you could also use the rule to comment on the linked issues as the problem record changes status to keep people up to date (either a public comment for everyone or an internal comment to update the assignee).
Hi @Tugrul Salli welcome to the Atlassian Community!
Great to see that you linked the 3 incidents to a problem for root cause investigation.
If there is no workaround for these incidents, do you have a specific status in the workflow to indicate this? Something like Pending?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In my opinion, incidents without a workaround which are pending root cause analysis (handled in the problem ticket) should be transitioned to that status so the support team knows it doesn't need to work actively on those issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is it not possible to hide the incidents after they have been linked? Let's assume that there are a lot of such incidents because the customers are busy and open tickets :P . We then link all the tickets to a problem ticket and change the status to pending. then i would want the incidents to be out of the overview because otherwise the queue is overloaded.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do you want to hide all incidents with the status of pending? That would be easy, but I'd be surprised if that's what you want. It sounds like you want to hide pending incidents linked to a problem, but even then, when the problem is resolved, does that automatically close the incident or do you need to pay attention to it again?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Not all incidents, only those that have been linked to a problem should be hidden and when the problem is solved, all incidents should be closed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are you open to adding a status to your workflow? You could use automation to move incidents with a linked problem from "Pending" to a new status ("Pending Problem Resolution" or something like that) which you could exclude from your queue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yeah, sure, we can try it that way and i will add a status. Thanks for the suggestion (also for the first one). Could you give me a tip on how to exclude certain content?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
All you need to do is edit the queue to exclude issues in the new status.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As recommended by both @Paul Krueger and @Dave Mathijs , moving those issues in question to a different WF status and then modify/customize your queue configuration are something that we are doing in our instance. We have another queue setup to track those issues, so those issues are not being lost in the fix by the JSM agents.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Infrastructure Applications Team
Viasat Inc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Many thanks to all. I will implement the proposed solution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.