Counting transitions to a specific status in the time trend

[MJ Y97]

Hello everyone,

I want to make a report (or a dashboard with gadgets) to show the time trend of inputted issues to a specific status in a specific interval but i have no clue to do that.

To clarify my question :

• If an issue enters that specific status 3 times on 3 different dates, it will count 3 times in my trend report.

OR

• if an issue has entered that specific status 3 times in one day, it should be counted 3 times for that date in the report.

Thank you for sharing with me if you have a solution

Regards.

[Valeriia_Havrylenko_SaaSJet]

Hello @MJ Y97    👋 

As an alternative , I guess you can try Time in Status for Jira Cloud (developed by my SaaSJet team) with 7 types of status time reports. 

For your exactly need we have Status Count report or Transition Count report

The Status Count report shows how many times an issue has been in each status.

Chart view of report:

The Transition Count report shows how many times an issue has moved between all statuses in the workflow.

Chart view of report:

Add-on has a 30-day free trial version and free up to 10 users. 
Please, let me know if you have any questions

Hope it helps 😌
Valeriia

[Bloompeak Support]

Hi @MJ Y97

Welcome to Atlassian Community!

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. For your case, you can have a look at Status Count And Entry Dates report.

• 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.

Hope it helps.

[Emre Toptancı _OBSS_]

Hello @MJ Y97 ,

The report you mentioned is an interesting one. It requires grouping issue history data not based on a date value on the issue but based on dates of individual status transitions. I am not aware of an easy option to do this in Jira (either with an OOTB feature or a marketplace app)

The closest thing would be to count the transitions of issues and group issues by a date value on the issues (like created date or resolution date). You can do this with a marketplace app.

If you are OK with using a marketplace app for this, our team at OBSS built Time in Status for this. It is available for Jira Server, Cloud, and Data Center.  

Time in Status mainly has several types of time reports but the app also has Status Count and Transition Count reports. These reports show how many times each status and each transition was used by each issue.

For all numeric report types, you can calculate averages and sums of those values grouped by the issue fields you select. 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 screenshot below shows a trend report sample for durations but you can do the same for status or transition counts)

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

[Madhu_RVS]

Hi @MJ Y97 

Welcome to the community !!

For a readymade solution, you can try out our plugin,

Time in Status Reports 

The add-on provides the time in each status for the entire lifecycle of the issue.

Also reports are available to track status count.

You can group multiple statuses and only include the ones you need to define a total combined time in those statuses.

Disclaimer : I work for RVS, the vendor for this app

[Mark Segall]

Hi @MJ Y97 and welcome to the community!

You may want to look into the native gadget Average Number of Times in Status.   While it is not exactly what you're looking for this will give you a trend analysis without the overhead I'm about to share.

Natively, this cannot be done.  I would recommend using the combination of automation and an issue type like a sub-task or, if you don't want to clutter up your project with transactional issues, you could capture this in a separate project and report against that project. It would work something like this:

• TRIGGER: Issue Transitioned To YourStatus
• ACTION: Create Issue
  This is just for the purpose of giving you something to track.  We'll capture the key in the summary so you have something to pivot against.
  
  • Summary: {{issue}}
  • Issue Links: Trigger Issue
• BRANCH: Recently Created Issue
  We're going to immediately close the issue
  
  • ACTION: Transition Issue (Closed)

You won't be able to run a report natively because Jira doesn't provide a gadget that allows custom line/bar charts.  So, you'll need to create a filter and export the results and use your spreadsheet app of choice to provide the desired reporting.

If you want something more elegant, you'll need to search the marketplace.