You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We recently introduce a new workflow and it seems to be skewing our time to Time to Resolution Report.
Anything set to this work flow seems to spike the time to resolution graph and have a much higher than normal elapsed time.
Initially, we thought this was because the workflow was set up in a way that didn't pause the timer. To get around this we would set priority to trivial removing the timer. However, even in cases where priority has been set to trivial, and the timer has been paused, we have seen larger than normal elapsed time figures.
Can any one explain why this might be?