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

Can you check two criteria for SLA in JSM

Ste404

Hi there,

Looking at SLA I was testing a first agent response. I can see you can stop the SLA when an issue moved from unassigned to assigned. You can stop the SLA when an issue moves into certain status.

Is there a way to combine the two, stop the SLA counter when the issue is assigned AND is moved to In Progress?

Trying to avoid the SLA stopping if an issue is just moved to in progress but there is no-one assigned.

Accepted answers

All comments

Joseph Chung Yin

@Ste404

You can create your custom SLA rule and associate multiple conditions for Stop SLA counting (see image below)

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

Ste404

That is pausing the SLA, I don't see them in the finish SLA. If it is just paused that means when it moves out of In Progress it would start counting again?

Brant Schroeder

@Ste404

What @Joseph Chung Yin provided is correct. The conditions are all in the same place. You can create your custom rule for start, pause or finish.

Screenshot 2022-09-07 225521.jpg

Ste404

Assignee: Set and Status: In Progress are not options like that.

In 'Finish Counting' they are worded differently and then act individually.

For finish I had "Assignee: From Unassigned" and also had "Entered Status: In Progress"

That meant I could do either one.. it stopped if the status went to In Progress but was unassigned.

I can't see the same settings in Pause and Finish.

Joseph Chung Yin

@Ste404 -

You can add other conditions for Start/Pause/Finish events

I would recommend you to test it out.

Best, Joseph

Connor_lld39i

Hi @Ste404 Joseph and Brant are correct in that you can add multiple conditions for pausing/finishing an SLA. BUT as you've discovered those conditions are evaluated as OR not AND. So the SLA count will stop when the issue is assigned OR it will stop when the issue transitions to in progress.

Ste404

Thanks for confirming what I thought, frustrating you can't use JQL or the like as a condition to build a specific AND scenario.

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