Our development team relies a lot on the chart resolution time for bugs raised by our customers. Many a times some of the bugs are blocked due to third parties.
However, since the way resolution time is calculated (open to resolved status time), the metric does not show us the real picture.
Even if one bug took 5 min to fix but was waiting for another 3rd party for 2 months, the resolution time shows 2 months , which is not true.
I know service desk allows you to stop the timer and lets you calculate a similar metric. However, considering the cost service desk is not an option for us.
Is there any other alternative to this. Any workaround any one might want to suggest?
We've created a specific plugin for our customer to calculate those SLA rules (with automatic acceptance based on conditions) that will put ticket on delay when it is in certain statuses. So haven't found good existing generic solution that will satsify the requirements. So maybe you should look into development / order of such kind of feature.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs