How to get the time of each transition?
Asked by ???:

Hi, I creat some custom field.

creattime is for the time the issue is created.

todotime is for the time when the issue is transitioned to todo.

canceltime is for the time when the issue is transitioned to cancel.

donetime is for the time when the issue is transitioned to done.

Then, creattime is equivalent to the createddate, but the others?

Is there any smart value or other ways?

Thanks


Answers:
author: Valeriia_Havrylenko_SaaSJet
body: Hi [@???](/t5/user/viewprofilepage/user-id/5205943) ?  

I guess you can try [Time in Status](https://marketplace.atlassian.com/apps/1219732?utm_source=atlassian+community&utm_medium=referral&utm_campaign=Comment_How-to-get-the-time-of-each-transition_20230724)(developed by my team).

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/325951i1FCAA064F1605239/image-size/large?v=v2&px=999 "image.png")

The primary purpose is to help teams gather valuable data about the lifecycle of your issues in Jira. Add-on allows you to measure and **visualize the time spent in each status**, such as "Open," "In Progress," "In Review," and "Closed. But also you can call them as a "creattime", "todotime", "canceltime", "donetime". Add-on provides **7 types of reports** to help you identify areas for improvement.   

![Time in status GIF.gif](https://community.atlassian.com/t5/image/serverpage/image-id/268612i4311D712CED3B22A/image-size/large?v=v2&px=999 "Time in status GIF.gif")  

Add-on has a [**30-day** free trial](https://marketplace.atlassian.com/apps/1219732?utm_source=atlassian+community&utm_medium=referral&utm_campaign=Comment_How-to-get-the-time-of-each-transition_20230724) version and [**free up to 10 users.**](https://marketplace.atlassian.com/apps/1219732?utm_source=atlassian+community&utm_medium=referral&utm_campaign=Comment_How-to-get-the-time-of-each-transition_20230724)  
Please, let me know if you have any questions

Hope it helps ?


author: Emre Toptanc? _OBSS_
body: Hello [@???](/t5/user/viewprofilepage/user-id/5205943) ,

Jira keeps all transition dates in each issue's history but those values can't be obtained as an issue field. On any issue, you can only get create, resolution, and last updated dates as system fields.

For better flexibility and maximum details, our team at OBSS built [Time in Status](https://marketplace.atlassian.com/apps/1211756/) for this exact need. It is available for Jira Server, Cloud, and Data Center.

Time in Status mainly allows you to see how much time each issue spent on each **status** or each **assignee**. The app also has date reports that show transition dates for each status

![tisCloud_StatusDuration_LeadTime_with Estimates.png](https://community.atlassian.com/t5/image/serverpage/image-id/170015i6CBCFEFDC1640B76/image-dimensions/215x97?v=v2 "tisCloud_StatusDuration_LeadTime_with Estimates.png") ![tisCloud_AssigneeDuration.png](https://community.atlassian.com/t5/image/serverpage/image-id/246449iA6FF27980A832D08/image-dimensions/199x96?v=v2 "tisCloud_AssigneeDuration.png")

![tisCloud_FirstTransitionToStatusDate_Report.png](https://community.atlassian.com/t5/image/serverpage/image-id/261728iACD6415083E61763/image-dimensions/186x95?v=v2 "tisCloud_FirstTransitionToStatusDate_Report.png")

Most of the time, customers want those dates to get some time metrics. Time in Status will help you with that too. You can combine the time for multiple statuses to get metrics like **Issue Age, Cycle Time, Lead Time, Resolution Time** etc.

For all numeric report types, you can calculate **averages** and **sums** of those durations grouped by the issue fields you select. For example total in-progress time per *customer*or average resolution time per sprint, week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) or sprints is particularly useful here since it allows you to compare different time periods or see the trend.

![tisCloud_StatusDuration_LeadTime_Average_TimeGrouped.png](https://community.atlassian.com/t5/image/serverpage/image-id/170014i3A4C82B8C3EE58D2/image-dimensions/235x72?v=v2 "tisCloud_StatusDuration_LeadTime_Average_TimeGrouped.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 Company Managed and Team Managed projects for Jira Cloud.

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.

![Gadget_AverageStatusDurationByComponent.png](https://community.atlassian.com/t5/image/serverpage/image-id/170017i541738A81A7EBA80/image-dimensions/165x135?v=v2 "Gadget_AverageStatusDurationByComponent.png") ![tisCloud_StatusDuration_LeadTime_Chart.png](https://community.atlassian.com/t5/image/serverpage/image-id/170018i88B62F9CBD7B6C6E/image-dimensions/198x94?v=v2 "tisCloud_StatusDuration_LeadTime_Chart.png")

<https://marketplace.atlassian.com/apps/1211756/>

EmreT


author: Mehmet A _Bloompeak_
body: Hi [@???](/t5/user/viewprofilepage/user-id/5205943)

You can try [Status Time Reports](https://marketplace.atlassian.com/1221826) 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](http://status-time.bloompeak.io/demo), you can see it in action and try without installing the app. For your case, you can have a look at [Status Count And Entry Dates](https://bloompeak.atlassian.net/plugins/servlet/ac/io.bloompeak.status-time/st-report?ac.reportid=1277) 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.

* This app has a dynamic status grouping feature so that you can generate various valuable reports as time in status, time in assignee,**status entry dates and status counts,**cycle time and lead time, average/sum reports by any field(e.g. average in progress time by project, average cycle time by issue creation month).

* You can search issues by Project, Issue Type, Status, Assignee, Issue Creation/Resolution Date(and any other Date field) and JQL Query.
* Status durations are calculated according to the working calendar you define. Once you enter your working calendar into the app, it takes your working schedule into account too. That is, "In Progress" time of an issue opened on Friday at 5 PM and closed on Monday at 9 AM, will be a few hours rather than 3 days.
* You can set different duration formats.
* You can export reports in CSV file format and open them in MS Excel.
* You can also add this app as a gadget to your Jira dashboards and reach "Status Time" from Issue Detail page.
* You can enable/disable access to Status Time reports\&gadgets and Issue Detail page per project, users, groups or project role.

If you are looking for a completely **free** solution, you can try the limited version [Status Time Free](https://marketplace.atlassian.com/apps/1222051).

Hope it helps.


author: Ollie Guan
body: Hi [@???](/t5/user/viewprofilepage/user-id/5205943) ,

Record these datetimes and backfill in the workflow post function or you can try some free plugins.  

[https://marketplace.atlassian.com/apps/1211756/time-in-status?hosting=cloud\&tab=overview](https://marketplace.atlassian.com/apps/1211756/time-in-status?hosting=cloud&tab=overview)

[https://marketplace.atlassian.com/search?hosting=cloud\&moreFilters=freeStarterTier\&product=jira\&query=transition%20date](https://marketplace.atlassian.com/search?hosting=cloud&moreFilters=freeStarterTier&product=jira&query=transition%20date)

comments: author: ???
body: [@Ollie Guan](/t5/user/viewprofilepage/user-id/853638)

I know that it can be done by post function, but it is only for new transition.

What about the old issues?

I want to set some smart values through automation, but I don't know what values can be used.


Tags: cloud

jira-work-management-cloud