Jira to allow using StatusChangedDate in JQL

[Anita Chitragar]

In JQL, Currently statusCategoryChangedDate is available but statusChangedDate field is not available. 

Sprint status check and Sprint retrospection can benefit with availability of data on how long it takes to move a task from one status to another. There is no built in gadget to configure specific status and get graph/report on this.

Similar to statusCategoryChangedDate field in JQL, requesting Jira Product owner to add statusChangedDate in roadmap so that Jira user can create filters to help identify tasks taking longer than expected and make necessary changes to address the root cause for the delay.

[Meghan LaClair]

Hi @Anita Chitragar 

We solve for this at minware by automatically calculating velocity at the task level and providing alerts for tasks that take longer than expected.

We combine version control, ticketing, and calendar data into one plug and play dashboard to provide full transparency. 

We offer a free trial if you want to check us out!

Disclaimer: Marketplace Partner

[Hannes Obweger - JXL for Jira]

Hi @Anita Chitragar

if you're open to solutions from the Atlassian Marketplace, your use case might be solvable with the app that my team is working on, JXL for Jira.

JXL is a full-fledged spreadsheet/table view 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 “smart columns” that aren’t natively available, including the status changed date. 

This is how it looks in action:

As you can see above, you can easily sort and filter your issues by the status changed date. You can also use it in JXL's advanced features, including issue hierarchies, issue grouping, sum-ups, or conditional formatting.

Once you've narrowed down your list of issues, you can work on your issues directly in JXL, trigger various operations in Jira, or export your issues with just one click.

Best,

Hannes