Duration between status when the ticket never moved to a intermediate status

[santosh kumar gorle]

Hi,

I am trying to export the data for Duration between statuses but there are few tickets which were never moved to an intermediate status. The application is considering todays date for the intermediate status and giving a huge duration. 

Is there any way it can take the date from the next transition status similar to the Actionable Agile

[Karolina Wons_SaaSJet]

Hello @santosh kumar gorle 

If you're ok with the third-party add-ons, I recommend you to try Time between Statuses. It fits your needs perfectly and can track time between statuses even if the tickets have never moved to intermediate status.

This add-on is developed by my team and is free for using up to 10 users. Let me know if you have any questions.

Hope it helps.

[santosh kumar gorle]

Hello @Karolina Wons_SaaSJet 

Thank you for your response. i am already using Time in Status Plugin. My question was to address a specific situation with in the available reports of that plug in.

Duration Between Status is one of the report which i am interested. In my project the available status are Open, Analysing, Backlog, Development ,Done

For few tickets, The status was moved from Open to Backlog directly skipping the analysing status.

When i am trying to calculate the Open to Analysing "Duration Between Status", the plug-in is considering Analysing status date as today and giving the time difference between the same. Is there any way i can force the plugin to consider the Transition date of backlog movement if analysing status does not exists for that ticket.

Please help me with the same.

Thanks in Advance.

[Emre Toptancı _OBSS_]

Hello @santosh kumar gorle

There are several apps in the marketplace with similar names. Which one are you using? Who is the vendor?  (It would be best if you could attach a screenshot)

And also, are you using Jira Server or Jira Cloud?

Thanks.

[Bloompeak Support]

Hi @santosh kumar gorle

Welcome to Atlassian Community!

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. You can group statuses and include only the ones that you want to track/see in your report.

• This app has a dynamic status grouping feature so that you can generate various valuable reports as 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.

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

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.

[santosh kumar gorle]

Hello @Bloompeak Support 

Thank you for your response. i am already using Time in Status Plugin. My question was to address a specific situation with in the available reports of that plug in.

Duration Between Status is one of the report which i am interested. In my project the available status are Open, Analysing, Backlog, Development ,Done

For few tickets, The status was moved from Open to Backlog directly skipping the analysing status.

When i am trying to calculate the Open to Analysing "Duration Between Status", the plug-in is considering Analysing status date as today and giving the time difference between the same. Is there any way i can force the plugin to consider the Transition date of backlog movement if analysing status does not exists for that ticket.

Please help me with the same.

Thanks in Advance.

[Emre Toptancı _OBSS_]

Hello @santosh kumar gorle , 

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. 

Status reports have 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.

       

Time in Status also has Duration Between Statuses report type which shows the duration from issue creation to a specific status or the duration between two specific statuses. This report type also allows you to select the intermediate statuses whose durations will be excluded from the report.

  

Time in Status has Custom Calendar function which allows you to create as many different working calendars as needed and get reports based on them. Time in Status can also report on resolved and non-resolved issues together.

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