nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Hide linked issue in the queue

Tugrul Salli

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?

Accepted answers

Dave Mathijs

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?

Paul Krueger

I think I'd,

Set up a custom short text field for your incident request type that keeps track of the status of the linked problem.
Create an automation rule triggered when the problem changes status. For linked issues, if they are incidents, update the custom field with the new status.
Modify your incident queue to exclude issues with values in the custom field as needed (so, if the problem status is "pending", the custom field value will also be "pending", therefore you can exclude issues where the custom field value is "pending."

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).

Joseph Chung Yin

@Tugrul Salli -

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.

All comments

Dave Mathijs

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?

Tugrul Salli

Hi @Dave Mathijs, thanks for the quick reply.
Yes we have the status pending in our workflow.

Dave Mathijs

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.

Paul Krueger

I think I'd,

Set up a custom short text field for your incident request type that keeps track of the status of the linked problem.
Create an automation rule triggered when the problem changes status. For linked issues, if they are incidents, update the custom field with the new status.
Modify your incident queue to exclude issues with values in the custom field as needed (so, if the problem status is "pending", the custom field value will also be "pending", therefore you can exclude issues where the custom field value is "pending."

Tugrul Salli

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.

Joseph Chung Yin

@Tugrul Salli -

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

Tugrul Salli

Many thanks to all. I will implement the proposed solution.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management