I need to know how I can filter the incidents that are in the same state for more than x days, or that have not changed the state for x certain days
-----------
For example.
I want to know how many incidents have been in the "in progress" status for 10 days or whatever date I want to set.
Hi Josu,
Thank you for your question.
I the native JQL search in Jira you could run a query like issuetype = Incident and status = "In Progress" and status changed to "In Progress" before -10d
In this query you can change the -10d to the number of days to check for an you can change the name of the issue type and status as you need.
I hope this helps.
Regards,
Kristian
With that solution, I think it adds all the times it goes to the state I'm trying to filter, which in this case is "waiting for user".
The final idea is the following, which I show you in case you have any other alternative.
I want to make an automation in which if a ticket spends more than 10 days in "waiting for user", it will be automatically closed.
To do this I have to filter that ticket search, which is what I'm asking now. I have found this sentence, if you can tell me if it is also valid:
status = "waiting for user" AND NOT Status changed after startOfDay(-10)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Josu,
That JQL should work but you could also something like status changed to "Waiting for user" before startOfDay(-10)
Regards,
Kristian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Josu
if you're open to solutions from the Atlassian Marketplace, I think you might like the app that my team and I are working on, JXL for Jira.
JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a number of so-called history columns that aren't natively available, including the time since status change, time in [status], or time between [status] and [status].
With these, you can build a view like e.g. this in just a couple of clicks:
As you can see above, you can easily sort and filter by all your issue fields and history columns. You can also use them across JXL's advanced features, such as support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting.
Any questions just let me know,
Best,
Hannes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Josu 👋
I suggest take a look at article Jira Status Change Data: The easiest way to display and extract. There i suggest 2 ways to get status changes by date.
Also you can get status changes by JQL query:
status changed from "Open" to "In Progress" during ("YYYY-MM-DD", "YYYY-MM-DD")
Replace "YYYY-MM-DD" with the desired start and end dates for your analysis.
And more easiest and enhanced option is The Status Entrance Date report (Time in Status for Jira add-on) that shows the date an issue has moved to a particular status.
With this report you will get dates when the issue has entered each of the statuses on the grid as it’s shown below.
On the chart, it shows the number of tasks that have entered a status on a certain date - for example, 1 task out of 5 tasks has entered the Progress status for the first time on the 23-rd of May.
Add-on has a 30-day free trial version and free up to 10 users.
Hope it helps 😌
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Update on May 9th, 2024: Time in Status by OBSS was recently rebranded as Timepiece. It is still the same capable app with the same dedicated team behind it. The answer below mentions the app as "Time in Status" but you can find the app in the marketplace as "Timepiece (formerly Time in Status)".
Hello @Josu ,
Welcome to the community!
I have a suggestion that will help you achieve your desired results more easily. You can create filters and reports effortlessly by using a third-party application.
If you are open to using an application specifically tailored to your needs, Time in Status which is developed by my team at OBSS, is the tool I would highly recommend. It is available for both Jira Cloud, and Data Center.
Time in Status mainly allows you to see how much time each issue spent on each status or each assignee. As you can easily track the time spent on statuses, you can also easily filter the results.
Here is an example that aligns with your needs.
If you select the status duration report for a particular project in Time in Status and apply a filter to identify incidents that have been in the 'in progress' status for more than 10 days, you will receive the results within seconds. (Please see the screenshots below)
Visit Time in Status to explore how our JIRA add-on can revolutionize your metrics measurement process. Enjoy a 30-day free trial to experience the full range of features.
Hope it helps,
Gizem
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Josu ,
Do you only need to see the issues that are in "In Progress" status now and have been in "In Progress" status more than 10 days? If so, the JQL provided by @Kristian Walker _Adaptavist_ perfectly matches your need.
If you also need to see the issues that are in "Closed" status now but have been "In Progress" status more than 10 days, then 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.
If you are looking for a completely free solution, you can try the limited version Status Time Reports Free.
Hope it helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.