nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Find number of issues that entered a particular status in a month regardless of current status

Alec Dewell

I am using JIRA product discovery and want to share the following

How many new ideas were managed in a month (easy issues created)
How many ideas were 'rejected' in a month
How many ideas were 'validated' in a month

I can do the first one no problem but I find it hard to look at when an idea entered a particular stage within a time period. I don't care what its current stage is just which one it entered.

Has anyone solved this (without buying something on the marketplace) the alternative would be to do something in Python. Which is fine but last resort.

Accepted answers

Bill Sheboy

Hi @Alec Dewell -- Welcome to the Atlassian Community!

Please try using the JQL operator WAS IN with DURING for that: https://support.atlassian.com/jira-software-cloud/docs/jql-operators/#WAS-IN

Or the CHANGED TO operator to detect when the change occurred: https://support.atlassian.com/jira-software-cloud/docs/jql-operators/#CHANGED

For example,

project = myProjectName
 AND status CHANGED TO "In Progress" DURING (startOfMonth(-1), endOfMonth(-1))
 ORDER BY Key ASC

This would find the issues changed to "In Progress" during the prior month. Specific dates or other date functions may be used in DURING, so adjust this as needed.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Alec Dewell -- Welcome to the Atlassian Community!

Please try using the JQL operator WAS IN with DURING for that: https://support.atlassian.com/jira-software-cloud/docs/jql-operators/#WAS-IN

Or the CHANGED TO operator to detect when the change occurred: https://support.atlassian.com/jira-software-cloud/docs/jql-operators/#CHANGED

For example,

project = myProjectName
 AND status CHANGED TO "In Progress" DURING (startOfMonth(-1), endOfMonth(-1))
 ORDER BY Key ASC

This would find the issues changed to "In Progress" during the prior month. Specific dates or other date functions may be used in DURING, so adjust this as needed.

Kind regards,
Bill

Gizem Gökçe (OBSS)

Hello @Alec Dewell ,

Welcome to the community!

As @Bill Sheboy mentioned above it is best you use the WAS IN operator and create a custom JQL query with specific dates on it to get the numbers you want.

However, it will be hard for you to write down a separate JQL for every month and keep all the records together.

I see that you are not looking for a paid solution right now. However, if you ever need it I can recommend Timepiece - Time in Status for Jira which is built by my team at OBSS. It is available for both Jira Cloud, and Data Center.

Our app has a free 30 day trial and is free for up to 10 users. So please feel free to give it a try and present it to your management team.

Time in Status mainly allows you to see how much time each issue spent on each status or each assignee.

Although at first glance it may seem that the application is only used to calculate durations, this is far from the truth. This feature is just the tip of the iceberg. The application has a reporting option called Aggregated Reports where you can get the total number of issues you requested and group them in a single report.

For example, for your case, I have compiled a report and included the screenshot below for your examination. I've used a custom JQL to filter the issues within a project that were in the Reopen and In Progress states, and group the issues according to the month and year they were created.

WAS IN OPERATOR.png

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 for Jira Cloud.

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.

Timepiece - Time in Status for Jira

Hope it helps,

Gizem

Mehmet A _Bloompeak_

Hi @Alec Dewell

Welcome to the Atlassian Community!

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 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, resolution 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.

Alec Dewell

Thanks Bill, that is exactly what I want. Really appreciate the help.

Alec

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

jira-product-discovery