Write a JQL to workout the time spent in all our in progress statuses except for ready for releaese.

[Ryan Jones]

We have a column named 'Ready for Production' where we move our tickets to prior to being done. 

The tickets completed in the previous sprint get carried over to the next sprint to allow for release on to staging and to release into prod.  Because they don't move to done until a coupe of days in the next sprint I am struggling to measure an accurate cycle time, throughput and  velocity.  

I want to wrote a JQL to include certain issue types (bugs, features, stories) not sub-task and only include the in progress columns with the exception of 'Ready for Production' column and between the dates of our sprints.  

[Mehmet A _Bloompeak_]

Hi @Ryan Jones

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. It also 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).

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

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.

Hope it helps.

[Madhu_RVS]

Hi @Ryan Jones 

For a readymade solution, If you are open for a mktplace app, 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.

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

Do try it out.

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

[Emre Toptancı _OBSS_]

Hello @Ryan Jones ,

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

[Bill Sheboy]

Hi @Ryan Jones 

For your scenario you note:

Because they don't move to done until a coupe of days in the next sprint I am struggling to measure an accurate cycle time, throughput and  velocity.

Those measures are often described as...

• Cycle time: the duration from start of a specific status to a different specific status.  For example, Build Cycle Time could be from the start of in-progress until completed.
• Throughput: the count of items completed per unit of time
• Velocity: a measure of completed items, often as some measure of size per unit of time

You also describe your workflow as items start in one "sprint" and release in another.  Jira project reporting is based on the board filter, and sprint boundaries for scrum boards.  And so I would expect each of those measures to reflect that duration/sprint boundaries.

Are you perhaps trying to measure (and manage) something different?  Thanks!

Kind regards,
Bill

[Ryan Jones]

[Ryan Jones]

[Ryan Jones]

[Vamsi Kandala]

Hi @Ryan Jones

Welcome to the community!

Can you try this?

project = "Project Name" and issuetype in (Story, Task) and status in ("In Progress") and Sprint in (Sprints separated by Comma)

Hope this helps.

Thanks,
Vamsi

[Ryan Jones]

@Vamsi Kandala Thank you very much for your help, I have tried everything above and it is still not working.  

I have tried two options and both did not work

1. "Sprint IN openSprints()"

2. "Sprint = 42

Ryan

[Vamsi Kandala]

Hi @Ryan Jones,

Is it possible to post your JQL query here along with the screenshot of the results?  Can you mention which tickets should or should not be part of the results?  That way, we can get more clarity.

Thanks,
Vamsi