Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,459,104
Community Members
 
Community Events
176
Community Groups

Why SLA is restarting?

Since we've migrated our jira to cloud, i could realise the SLA Time to Resolution is always restarting when a ticket is reopened,  However, this wasn't happening into the Jira Server.

 

I found something that might be the reason, although we had always the same configs, since the begining. In the workflow, it was made a config that when a ticket is reopened, the resolution will be cleared, as necessary to don't create any problem when searching for opened tickets. 

WORFLOW.png

 

But, when you look into the SLA configs, it was defined that the counting will start also when the resolution field be cleared, 

sla.png

 

Well, i would know please where we're making a mistake, and also how could we solve this, in order to when the next ticket be reopened, the SLA will keep counting where he was stopped, and not restarting again.

1 answer

1 accepted

1 vote
Answer accepted

Hi @Felipe Dorocinski ,

That is indeed normal behavior that a SLA restarts with thsese START and STOP conditions.

The only way to fix this is to:

  • remove the start condition on the "Resolution: Cleared"
  • move the Resolution: SET to the Pause condition.

 

This way when you have a resolution set it will pause the timer (you will need to add a new STOP condition, like a Closed/Done status) and it will continue to count when the resolution is cleared aka no longer set.

That atleast is how I resolve this (without any addons)

This works like that to be able to do "multi cycle SLA's" which is normally not what you want for these..

https://confluence.atlassian.com/servicemanagementserver/example-creating-an-sla-with-multiple-cycles-939926419.html

Hi @Dirk Ronsmans 

I would like to thank you for your help! I made the changes suggested and could realise that its working well again!

 

Have a nice week! :D

Like Dirk Ronsmans likes this

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events