Hey JIRA community :
In my board , I have defined 6 status (To do , in progress,In QA ,Blocked , In review , Done) and I will ask the team members update their assigned issues to the newest status and at last update to the "Done" status when the issues is completed.
My question is , how can I know the exact time of when a issue is changed to a specific status? For example , when it is updated to "Done" status.
Hi @daniel.ouyang 👋
Welcome to the Atlassian community!
You can do it with Time in Status add-on. Just simply:
Table view:
Chart view:
For more in-depth data analysis, you can create reports as pivots. For example, you can look at the percentage of time spent in different statuses.
Dashboards gadgets feature will keep your finger on the pulse and track team productivity in real-time.
For Scrum teams we are also offering Sprint Report feature in Time in Status
Add-on have 30-day free trial, free up to the 10 users and developed by my team.
I hope you find this helpful 🚀
Hi Daniel - Welcome to the Atlassian Community!
A simplest answer is to go to the issue and click on the history tab in the activity section at the bottom of the screen. There you can see in the history who moved it to Done and the exact time it was done.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You are right , John . But what I want is to view this date as a column in the issue list like here , do you hava any idea how can I achieve this and get this date ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@daniel.ouyang , to be able to view the transition date as distinct field in the issue, you will have to create a custom field. You can use an automation to populate it automatically as I suggested.
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 !!
As suggested by other you can use Automation to capture this information.
Or you can use a third party app as well to get this data easily. If you are open to try out one, do take a look at
One of the many reports which the app provides is Status Transition Details, as you can see in the screen grab below. It displays the who transition the issue status and when.
The app has 20+ reports to meet a variety of time in status use cases.
Disclaimer : I work for the vendor who built this app
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.
Hi @daniel.ouyang , welcome to the Atlassian Community and thanks for your question.
You can use an automation for this. Here is an example rule that you could modify for your use case - https://www.atlassian.com/software/jira/automation-template-library#/rule/9918996
Instead of setting the Start Date, you could create a custom field of 'transition date' as a date type field and use the syntax from this rule to stamp the time when the transition takes place into the field - {{now.convertToTimeZone(issue.reporter.timeZone)}}
I hope this helps
Cheers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That is very helpful , could you show me how to create this automation rule and write the JQL ? Thanks in advance !
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Free Jira Cloud Plugin -
Issue Status Insights- Time in Status
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you are using Jira Cloud and want to have quick view to focus on status transition at issue level then you can use a free Jira Cloud Plugin
Issue Status Insights- Time in Status
Jira doesn’t provide an easy way to track how long an issue spends in each status, requiring users to sift through history logs. Issue Status Insight solves this by showing all status transitions in one place, automatically calculating time spent in each status, and offering an aggregated view of total time. While Board Insights focuses on stuck issues and provides broader reporting solutions, Issue Status Insight zooms in on individual issues, offering quick, detailed status insights directly at the issue level without needing to navigate to higher-level reports.
If you are using Jira Cloud and want to have quick view to focus on status transition at issue level then you can use a free Jira Cloud Plugin
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. I agreed with what John Funk (other community leader) suggested on simply using the issue's history tab in the activity section view the project Ui when viewing the issue. In my opinion, the simpler the better, unless you have other needs on knowing the transition dates for statuses movements further.
Hope this also helps.
Best, Joseph Chung Yin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I saw your reply to @John Funk thread, unfortunately if you need to see the transition date in the search results as a column, then you will need to create a custom field (date/time data type) and populate it properly (i.e. using automation rule or modify your WF transition with a post function call etc...
Once it is done, then you can use it as a column in the search result. Hope this helps.
Best, Joseph
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! I agree with Valeria that using an automation rule may be the easiest if you want to use built-in functionality.
Alternatively, if you're open to solutions from the Atlassian Marketplace and/or don't want this to eat into your automation budget, you may want to have a look at 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 [status], 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. 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.
This all just works - there's no scripting or automation whatsoever required.
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.
Hello @daniel.ouyang ,
Welcome to the community!
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 (formerly Time in Status) , 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 (formerly Time in Status) 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.
@daniel.ouyang I agree with @John Funk , If I consider this to be the use case of letting someone know immediately about the change, the issue should be watched for the latest updates
https://support.atlassian.com/jira-software-cloud/docs/watch-share-and-comment-on-an-issue/#
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 Atlassian Community!
Jira doesn't have a built-in solution for the report you mentioned. If you prefer using 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. To get a report of when the issue entered a status, you can have a look at Status Count And Entry Dates report. Entry date(see In Development, Ready for Testing, In Testing, In Development columns) is status transition date and status count(see #In Development, #Ready for Testing, #In Testing, #In Development columns) is how many times an issue is entered to this status.
App Features:
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.
If you have any questions, feel free to schedule a free demo with us.
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.
Hi @daniel.ouyang Welcome to the Atlassian community.
This is not possible by defaultas Jira JQL or any gadget does not give the details about the time when the issue is transitioned to any status, you can found this details in the Jira history and create a custom script or scripted field to capture the date and time when issues status is changed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I agree with you Ravina ! But I am not very familiar with creating a custom script or scripted field to capture the date and time when issues status is changed , could you help me on this ?
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.