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; } } }

Regarding issue handling and timer

Jim Stewart_9b1rk3

I actually have two related questions that I got from HR in my quest to create documentation. My guess is it's a firm NO on both of these but due diligence requires that I ask.

1 If an issue is not picked up by an agent, can there be a timer that reassigns it or alerts someone if there is no action on it in X amount of time?

2. Is there a way to tag someone in an issue that will add it to their queue? My guess is that tagging will alert them but not add it to their queue as it is your contention there should be one assignee. And so the only way to put it in a new person's queue is to reassign it taking it out of the first assignee's queue.

Accepted answers

Jack Brickey

yes. You could use automation for that. I would set up a Time to First Response SLA and when the SLA breached I would assign to another agent. At least that is one way.
queues don’t need to have anything to do with assignment if you don’t wish. Queues can be defined by any query, e.g unassigned, labels, components, custom fields, pretty much anything. So decide on your needs and define issue and map to a queue as you need.

All comments

Jack Brickey

yes. You could use automation for that. I would set up a Time to First Response SLA and when the SLA breached I would assign to another agent. At least that is one way.
queues don’t need to have anything to do with assignment if you don’t wish. Queues can be defined by any query, e.g unassigned, labels, components, custom fields, pretty much anything. So decide on your needs and define issue and map to a queue as you need.

Jim Stewart_9b1rk3

Thanks for the info on the timer. I'm going to have to look into that a little bit.

As to queues, well the simplest thing is to have it default by assignee, at least as we are initially finding our way around in JSM. But the larger question is whether, say, one issue can be assigned to two people.

Jack Brickey

There is a lot of discussions in the Community around this and I would recommend you search/read for more details. Basically, Jira is designed to have a single assignee primarily for accountability. However, there are options. For example, you could create a ‘group’ user in Jira that represents multiple users or rather that two or more of your users need to watch. But that consumes a license. You could create a custom field to represent a team and leave the issue unassigned until one of the team members actually takes ownership. You could create an alternate assignee custom field.

Jim Stewart_9b1rk3

Hmm. Ok. I like the group idea. Good to know there are options. At the end of the day, it'll be HR's decision on which way to go but at least I can socialize these with them. Thanks

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