How can i calculate total time taken by a team to move jiras

[Jahnavi Pathak]

I need to calculate and compare time taken by Dev team and QA team. As of now i have 'Dev in progress' state then code goes to QA team to raise bugs in any issue, then ihe issue goes to 'deployment pending' state or assigned back to dev team based on no of bugs found. Is there JQL around this?

[Valeriia_Havrylenko_SaaSJet]

Hi @Jahnavi Pathak 
 
You can easily do it with Assignee time report in Time in Status for Jira Cloud (developed by my SaaSJet team) 

At the Assignee Time Report on the Column manager, you can manage the User Groups and compare them. 

You can Add a New Group

When you add a new one, write down a name to your custom column and add necessary users to a group



As a result, you'll get one column with summed data from your previously selected columns. 


Here is documentation.

This add-on has a 30-day free trial version and free up to 10 users.

Hope it helps 😌
Valeriia

[Jack Brickey]

Hi @Jahnavi Pathak , two possibilities I would offer:

• consider an addon app that measures/records Time in Status, here is a query in Marketplace- https://marketplace.atlassian.com/search?query=Time%20in%20status 
• leverage Automation and lots of custom fields to record the time in various statuses

For me, I would never leverage the second option because of the expense of using Automation and custom fields.

[Bill Sheboy]

Hi @Jahnavi Pathak -- Welcome to the Atlassian Community!

Adding to Jack's answer:

You could also see this information using the built-in control chart.  This report has some limitations, and I recommend trying it to see if it meets your needs.  https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-control-chart/

Kind regards,
Bill

[Mehmet A _Bloompeak_]

Hi @Jahnavi Pathak

Welcome to the Atlassian Community!

Unfortunately, it is not possible to extract Time in Status info with built-in JQL.

If you prefer to use a marketplace app, 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 Time in Status for Each Issue and Time in Assignee reports. For further details, you can have a look at Status Time Reports How to Videos.

• 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 completely free solution, you can try the limited version Status Time Reports Free.

Hope it helps.

[Emre Toptancı _OBSS_]

Hello @Jahnavi Pathak ,

Jira with its out-of-the-box features can't do this. You either have to build customer automation rules or use a marketplace app for this.

I can recommend Timepiece - Time in Status for Jira which is built by my team at OBSS. 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. 

       

Time in Status offers two report types for your case:

The first one is Status Duration report (please see the screenshot above) which shows how much time each issue spent on each status. You can combine status times to see measurements like Issue Age, Cycle Time, Lead Time, Resolution Time etc.

As an alternative approach, Time in Status also has Duration Between Statuses report type which shows the duration between two specific statuses. This report type also allows the user the exclude the times for "pause" statuses.

  

These reports show a list of issues by default so you can see the metric values for each issue separately. Also, for all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. For example total cycle 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.

All these report types, including averages and sums, can be turned into charts.

Time in Status 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.

  

Timepiece - Time in Status for Jira

EmreT

[Danut M _StonikByte_]

Hi @Jahnavi Pathak,

An easy way to do this, is to have a Cycle Time Trend chart/report split by weeks/months for each team.

You can easily do this by using the Cycle Time Trend gadget offered by our Great Gadgets app. 

This is an example of trend chart that shows the average of QA time in last 6 weeks, along with the trend and overall average:

To obtain this chart for QA, you have to configure the gadget to calculate the cycle time as time between entrance in "QA / Testing" status and entrance in "Deployment pending" status. Same approach for obtaining the DEV chart.

As an alternative to the Cycle Time Trend chart, you could also use the Control Chart gadget. This one has a similar configuration, but displays the issues that had a completed cycle along the time as a plot-chart, it displays overall average and allows you to set a threshold to easily identify the issues that took longer than expected (the ones in red-color).

These charts offer also a Data tab with a detailed report about the issues, which can be easily exported in CSV format.

 

This app offers many other useful gadgets, so it can be a great asset for your company. Take a look over the articles from our blog to make an idea about how many things you can track with this app. 

If you need any help, please don't hesitate to contact us at support@stonikbyte.com.

Danut.

[Amay Purohit_RVS]

Hi @Jahnavi Pathak 

Welcome to the community !!

As suggested by others an app can help you get this data. You can take a look at the one we have built

Time in Status Reports 

You can track the time taken in each status for the issues by each assignee.

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