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; } } }

Filters for historical statuses

Dorothy Callahan

Hi all,

Part of our workflow is to perform a validation after a deployment to ensure system is behaving as expected post deployment. If this fails, we return ticket to a post deployment validation failed. Is there a filter, or some other way, I can create to identify those tickets that have ever been in the post deployment validation failed status?

Thanks

Accepted answers

Amay Purohit_RVS

Hi @Dorothy Callahan

I believe you can get this data from history tab of the issues or use Jira Rest API's to get this information.

Also a mktplace app can help with a ready solution. If you are fine to try out one, you can take a look at

Time in Status Reports

The time in status report shows the status count report status during the entire workflow. So it will show how many times each issue has been in each status.

The app also has 20+ reports to track your bottleneck Issues & Processes.

Disclaimer : I work for the vendor who built this app

TIS - Count.PNG

Gizem Gökçe (OBSS)

Hello @Dorothy Callahan ,

To identify the tickets that have ever had a "post-deployment validation failed" status, you can write a JQL query using the WAS IN function.

For example in the JQL query below I've filtered the issues in my project which were in "In Progress" status at some point.

project = "My Scrum Project" AND status WAS IN ("In Progress")

You can use the WAS IN function to find out if a ticket has ever reached 'post deployment validation failed' status, but you will not be able to access information on how many times this action has been taken. At this point I would recommend that you move on to a third party application for more detailed analysis.

Timepiece - Time in Status for Jira which is developed by my team at OBSS, has several report types that will meet your needs. Our app is available for both Jira Cloud, and Data Center.

Time in Status mainly has several types of time reports (showing how much time each issue spent on each status, assignee, or group) 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.

STATUS COUNT REPORT:

Report Types Status Count.png

TRANSITION COUNT REPORT: Report Types Transition Count.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 Jira, JSM and JPD 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. Also you can export the reports in to various formats easily.

Visit Timepiece - Time in Status for Jira to explore how our JIRA add-on can revolutionize your reporting process. Enjoy a 30-day free trial to experience the full range of features.

If you wish, you can also schedule a live demo. We will provide a comprehensive overview of the application and address any inquiries you may have.

Hope it helps,

Gizem

All comments

Amay Purohit_RVS

Hi @Dorothy Callahan

I believe you can get this data from history tab of the issues or use Jira Rest API's to get this information.

Also a mktplace app can help with a ready solution. If you are fine to try out one, you can take a look at

Time in Status Reports

The time in status report shows the status count report status during the entire workflow. So it will show how many times each issue has been in each status.

The app also has 20+ reports to track your bottleneck Issues & Processes.

Disclaimer : I work for the vendor who built this app

TIS - Count.PNG

Gizem Gökçe (OBSS)

Hello @Dorothy Callahan ,

To identify the tickets that have ever had a "post-deployment validation failed" status, you can write a JQL query using the WAS IN function.

For example in the JQL query below I've filtered the issues in my project which were in "In Progress" status at some point.

project = "My Scrum Project" AND status WAS IN ("In Progress")

Timepiece - Time in Status for Jira which is developed by my team at OBSS, has several report types that will meet your needs. Our app is available for both Jira Cloud, and Data Center.

STATUS COUNT REPORT:

Report Types Status Count.png

TRANSITION COUNT REPORT: Report Types Transition Count.png

Visit Timepiece - Time in Status for Jira to explore how our JIRA add-on can revolutionize your reporting process. Enjoy a 30-day free trial to experience the full range of features.

If you wish, you can also schedule a live demo. We will provide a comprehensive overview of the application and address any inquiries you may have.

Hope it helps,

Gizem

Dorothy Callahan

Thank you. I believe the "WAS IN" will suffice as I don't expect any ticket to have gone into PDV failed status more than once. I will give it a try and if not providing enough detailed information I need, I will look into the third party app.

Gizem Gökçe (OBSS)

You're welcome! I am glad to hear that I was able to assist you. If you accept my answer, others with the same problem will see it at the top and we can help them too.

Have a nice day!

Hannes Obweger - JXL for Jira

Hi @Dorothy Callahan

if you're open to solutions from the Atlassian Marketplace, this would be easy to do using 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 range of so-called history columns that aren’t natively available, including number of times in [status].

This is how it looks in action:

As you can see above, you can easily sort and filter by your 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

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management