How to find the age of a user story in a particular state?

[Parveen Taj]

For example  'x' number of user stories are in "open" state, and 'y' number of user stories are in "in progress" state, now how to find the age of the ticket in that particular state. Can this be represented in dashboard with some chart?

[Lucy Warner_SaaSJet]

Hi @Parveen Taj 

To get the time issue spent in a particular state, you can try Time between Statuses (Server version) add-on.

1. Set the status you need to track the time in as Start and Stop timers.

2. Get the time spent in a particular status.

This add-on is developed by my SaaSJet team. Please, let me know if you have any questions. 

[Ismael Jimoh]

Hi @Parveen Taj 

I don’t know about if this can be shown on a dashboard but you can use the add-on Time in Status to get this information.

If you have scriptrunner, you can write a script to add a day each time an issue is in a specific status and display this on your dashboard.

Regards.

[Bloompeak Support]

Hi @Parveen Taj

As an alternative, you can try Status Time Reports app developed by our team. It mainly provides reports and gadgets based on how much time passed in each status.

Here is the online demo link, you can see it in action and try without installing the app.

• This app has a dynamic status grouping feature so that you can generate various valuable reports as time in status, time in assignee, status entry dates and status counts, cycle time and lead time, average/sum reports by any field(e.g. average in progress time by project, average cycle time by issue creation month).

• You can search issues by Project, Issue Type, Status, Assignee, Issue Creation/Resolution Date(and any other Date field) and JQL Query.
• Status durations are calculated according to the working calendar you define. Once you enter your working calendar into the app, it takes your working schedule into account too. That is, "In Progress" time of an issue opened on Friday at 5 PM and closed on Monday at 9 AM, will be a few hours rather than 3 days.
• You can set different duration formats.
• You can export reports in CSV file format and open them in MS Excel.
• You can also add this app as a gadget to your Jira dashboards and reach “Status Time” from Issue Detail page.
• You can enable/disable access to Status Time reports&gadgets and Issue Detail page per project, users, groups or project role.

If you are looking for a free solution, you can try the limited version Status Time Free.

Note: If you are interested in cycle and lead time, you can have a look at the article below.

Cycle Time and Lead Time in Jira: Productivity Measurement with Two Critical Parameters

Hope it helps.

[Emre Toptancı _OBSS_]

Hello @Parveen Taj,

If you are OK with using a marketplace app for this, our team at OBSS built Time in Status for this exact need. 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 and on each assignee. 

       

The app has Consolidated Columns feature. This feature allows you to combine the duration for multiple statuses into a single column and exclude unwanted ones. It is the most flexible way to get any measurement you might want. Measurements like Issue Age, Cycle Time, Lead Time, Resolution Time etc.

For all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. For example total in-progress time per customer (organization) or average resolution time per sprint, week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) or sprints is particularly useful here since it allows you to compare different time periods or see the trend.

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. It supports both Company Managed and Team Managed projects.

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.

And the app has a REST API so you can get the reports from Jira UI or via REST.

  

Using Time in Status you can:

• See how much time each issue spent on each status, assignee, user group and also see dates of status transitions.
• Calculate averages and sums of those durations grouped by issue fields you select. (For example, see average InProgress time per project and per issue type.)
• Export your data as XLS, XLSX, or CSV.
• Access data via REST API. (for integrations)
• Visualize data with various chart types.
• See Time in Status reports on Jira Dashboard gadgets

https://marketplace.atlassian.com/apps/1211756/

EmreT

[Parveen Taj]

Unfortunately I don't have these gadgets in JIRA , is there any other way ?

[Rahul_RVS_Support]

Hi @Parveen Taj 

If you are fine with a mktplace app, you can try out our add-on to get this data.

Agile Tools : Epic Tree, Links Tree, Time in Status & Worklogs

The main features are as below

• Multiple Time in Status Reports. Excel Export available for all status reports.
  
  • Time in Status
  • Time with Assignee
  • Time in Status with Assignee
  • Time with Assignee per Status
  • Status/Assignee Count
  • Multiple Transition Reports
  • Avg Time in status reports
  • Status Transition Dates Report
  • Time in Status Per Time Grain
  • Time with Assignee Per Time Grain
• Status grouping
• Save your reports
• CSV Export
• Multiple chart types
• Dashboard Gadget

[Parveen Taj]

Will this be applicable in below scenario.

Project A in JIRA has 400 stories

Project B has 180 user stories out of which 85 are linked to Project A stories.

Now will the Time in Status gadget can be used to create a dashboard for ONLY stories which are linked to Project A?

[Rahul_RVS_Support]

Hi @Parveen Taj 

Currently this feature is not available in the app.

But we can certainly add it to our backlog list and work on it.

To understand the use case better, you are looking to filter issues at multi level issue links hierarchy or only upto 1 level of hierarchy.

Thanks

[Parveen Taj]

For now looking at one level of linked issues hierarchy..