Inside every Item in JIRA you can zoom in into transition history, showing dates of each transition and the time/duration it has been in that state.
(JIRA Project)
It is possible to get these individual (or list) our of JIRA as a column in Jira Issue Filters ?
Case: I want to get the exact date an Item was moved into Backlog.
In Service Management we can use the SLA engine to determine that and configure it to our needs. But as far as i know it is not possible to use SLA in JIRA Project or ???
Any insight are welcomed.
I haven't done this myself, but you may be able to use Jira Automation to trigger a rule on status change, and then write the current date into a custom field; you could then search/filter by this custom field.
Alternatively, if you are open to solutions from the Atlassian Marketplace, there's a number of apps that could help with this. E.g., I believe that you use case would be very easy to solve 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 number of so-called history columns that aren’t natively available, including date of transition from [status] to [status], and many more.
This is how it looks in action:
As you can see above, you can easily sort and filter by your history columns, and 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.
You can also export your table to XLSX (i.e., Excel or Google Sheets) or CSV in just one click.
Any questions just let me know,
Best,
Hannes
Hello Hannes,
Thank you for your elaborate answer. Indeed the Automation of State transition is also on the top of our work around list... but good to have it confirmed...
It also confirms that the data is not exportable in a simple way, without going in via SOAP API, which we want to avoid.
Thanks also for the information on the PlugIn, it definitely looks interesting.
Our JIRA instance is global and Plugins are managed by group Function. I did post your video on our internal chatboards... just in case...
Again thanks for taking the time...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
no worries, I'm glad I could help! Let me know if there's anything else I can help clarify. Otherwise, if my answer is useful, kindly accept it so it is easier to find in the future.
Best,
Hannes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Hans van Rijsewijk 👋
For those of you looking for an add-on, I recommend trying out Time in Status
With the Time in Status report, you can get the duration the issue has been in each state
and with the Status Entrance Date report, you can obtain the dates of each transition.
Add-on has a 30-day free trial version and free up to 10 users.
Please, let me know if you have any questions
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.
Welcome to the community !!
If you are open to try out mktplace app for this need, take a look at
The Status Transition Dates report can help you meet this use case as shown below. You can also export this data to a csv file or a JSON feed which can be used in a BI tool like Power BI.
The app is free for 10 users. Do try it out.
Disclaimer : I work for RVS, the vendor for this app
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Amay,
Thanks for your answer, but as we are using a global JIRA Data Centre, Marketplace Apps are governed and controlled by Group Function.
Also we are looking for these fields to use in an alternate JIRA external reporting Dashboard.
We have solved the issue already via JIRA Automation rulez.
Greetings
Hans
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Hans van Rijsewijk ,
Welcome to the community!
You are correct, the required data is available in each issue's history but you will need to use a marketplace app to get ready-to-go reports. Good news that report is available in our application where you can directly learn the transition dates without having to deal with Jira issue histories. The app is Timepiece - Time in Status for Jira , the oldest and leading Time in Status app in Atlassian Marketplace, which is built by my team at OBSS. It is available for both Jira Cloud, and Data Center.
You can use the date-based reports to see the transition dates from/to a status. In the screenshot below you can see the transition dates of the issues to each status. I think this report will be spot on for your needs.
Visit Timepiece - Time in Status for Jira to explore and 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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Gizem,
Thanks for your answer, but as we are using a global JIRA Data Centre, Marketplace Apps are governed and controlled by Group Function.
Also we are looking for these fields to use in an alternate JIRA external reporting Dashboard.
We have solved the issue already via JIRA Automation rulez.
Greetings
Hans
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Hans,
I am happy to hear that your issue is resolved with the help of JIRA automation.
However, if there is a place where JIRA's automation capabilities are insufficient, our application is always there for you. Timepiece - Time in Status for Jira also has a very capable REST API. This means you can get the reports via REST and import the result to an external reporting tool.
In the future if you ever need assistance on this issue please feel free to reach out to us at appsupport.obss.tech or via email at appsupport@obss.tech.
Have a nice day!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Join the largest European gathering of the Atlassian Community and reimagine what’s possible when great teams and transformative technology come together. Plus, grab your Super Fan ticket now and save over €1,000 on your pass before prices rise on 3 June.
Register nowOnline forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.