How to get the time of each transition?

Question

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

Valeriia_Havrylenko_SaaSJet · Answer

Hi @靳光光  👋

I guess you can try Time in Status (developed by my team).

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.

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 😌

Emre Toptancı _OBSS_ · Answer

Hello @靳光光 ,

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 Timepiece - Time in Status for Jira 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

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.

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.

Timepiece - Time in Status for Jira

EmreT

靳光光 · Answer

@Ollie Guan

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.