am looking for a report for hours/days spent on each bug status (open, in progress, QA, closed) .. a kind of defect aging.
I tried gadget "Average Time in Status" which is not providing any thing.
pls help me
Hi @SriRameshNaidu Pataballa ,
The data you need is available in Jira Rest API. It provides the exact status transition date and time for each issue. It returns json, then you need to calculate it by coding which parses issue history rest api json for each issue.
Or you can search for marketplace apps which does the same for you. One of them is Status Time app developed by our team. It provides reports on how much time passed in each status and show status entry dates.
If you are looking for a free solution, you can try the limited version Status Time Free.
Seeing your posts/responses about being limited from adding marketplace addons/apps to the client instance, your options to do this type of reporting are quite limited. If the client is requesting the report, consider discussing marketplace apps with them to fill this need.
Otherwise, the work-arounds without addon apps could be:
Best regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As other community members mentioned here, a Jira app would do the job.
eazyBI is an app for data analysis and charts.
Using that, you can analyze, among other issue information, issue changelog data, including status transition analysis and time spent in each issue status.
There are a few examples in the eazyBI demo account for reporting on time spent in each status from different viewpoints, for example:
To get the report into your eazyBI instance, you can export the report definition and import it into your eazyBi account: https://docs.eazybi.com/eazybi/analyze-and-visualize/create-reports#Createreports-Exportandimportreportdefinitions
More information about eazyBI: https://docs.eazybi.com/eazybijira
If you have any questions or some assistance is needed with eazyBI, please, do not hesitate to contact us support@eazybi.com.
Ilze, eazyBI Customer Support Consultant
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @SriRameshNaidu Pataballa
This functionality is not available out of the box. You can try building this with custom fields and some post functions but that will be difficult to build and maintain. And that solution will work only for the issues after now.
In case you are OK with using a marketplace app, our team at OBSS built Timepiece - Time in Status for Jira app for this exact need. It is available for Jira Server, Cloud, and Data Center.
Time in Status allows you to see how much time each issue spent on each status or assigned to each assignee. You can also combine statuses into consolidated columns to see metrics like Ticket Age, Resolution Time, Cycle Time, or Lead Time.
You can calculate averages and sums of those durations grouped by the issue fields or time segments (For example, see the total InProgress time per Epic or average Resolution Time per month).
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.
Time in Status reports can be accessed through its own reporting page, dashboard gadgets, and issue view screen tabs. All these options can provide both calculated data tables and charts.
Using Time in Status you can:
Timepiece - Time in Status for Jira
EmreT
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi EmreT
I will not be able to make any changes to client restricted JIRA. thank you for quick response.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is no out of the box functionality for what you are seeking. The simplest way would be to use an app like https://wiki.almworks.com/documentation/structure/time-in-status-column-71042417.html
The other way, the more difficult, would be to create custom fields, do some automation calculations, while taking into consideration back-n-forth changes in the statuses.
I would go with the use of an app.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Alex, I am using the client owned JIRA and its restricted to install any plugins or third party apps. . any other better solution pls ? thank you for quick response.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the community !!
This data is difficult to get out of the box. If you would be interested in a ready made solution, one cheap and efficient solution that we have developed is Time in Status Reports . It lets you display the time in each status in an easy to read table, with configurable working hours setting. The app provides the following features
Time in Status :- More than 7 types of Time in Status reports to track your issues. You can also group your statuses to define your own cycle time/lead time/time to resolution
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rahul, thank you quick response. since am using the client owned JIRA and its restricted to install any plugins or third party apps. . any other better solution pls ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can try some other solutions to get the time in status data for Jira issues:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.