Good morning everyone
I have the following question: How can I get the total average of a series of SLA's, I have a total of 16 SLA's and I want to know the average of all of them.
I hope you can help me.
Hello @Administrador de Jira GA ,
SLA timers essentially measure the time between two points in issue history and those two points are usually when the issue transitions to a status. So it is (once again usually) possible to see it as the total time spent on one or more statuses. The solution I am proposing below does not directly match to SLAs but can help you with your reporting needs.
Our team at OBSS built Time in Status for similar needs. It is available for Jira Server, Cloud and Data Center.
Time in Status mainly allows you to see how much time each issue spent on each status or assigned to each assignee. You can combine statuses in any way into consolidated columns to see metrics like Resolution Time or Ticket Age. You can calculate averages and sums of those durations grouped by issue fields you select. (For example see the monthly average Resolution Time per user, or weekly average Response Time per component, etc.).
Time in Status can display its reports and charts in its own reporting page, in dashboard gadgets and in a tab on issue view screens.
The app calculates its reports using already existing Jira issue histories so when you install the app, you don't need to add anything to your issue workflows and you can get reports on your past issues as well.
Using Time in Status you can:
I have the bad / good habit to try and understand why people want to do certain things and what problem they are trying to solve. In this case, I am struggling a bit with that :-).
If you have 16 SLA's, is that because you have a really large workflow that you split into several smaller pieces (e.g. time to response, time in 2nd line, time waiting for vendor, time waiting for customer, time in 3rd line, time in testing, time to release, ...) and would like to calculate an overall average lead time or time to resolution over all those stages?
Or do you have different SLA's for different issue types / request types and / or priorities and you want to set up an average over everything?
Technically, the easiest solution would probably be to set up a 17th SLA that covers all your tickets and runs across the entire process of all those tickets. The standard average SLA report can produce the numbers, in that case.
Thanks for your answer.
In cash, I have different SLAs for each category of incident, since it is not the same time of attention from a damaged keyboard incident to a damaged incident in a database.
And sorry, I don't think a general SLA works for me, since my response time for the longest SLA is 270 hours, or maybe I don't understand how it would be.
Hello Atlassian Community! We’re thrilled to announce some exciting changes to incident management in Jira Service Management Cloud, in order to give your teams extra muscle during incidents, and ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events