Turn Around Time in Issue Navigator

[Swaroop Bangera]

Hello,

I also want to take a moment to thank this community for helping. I am able to learn a lot new things. I have learning to Create a Issue Age columns just by finding similar issue responses. And am able to create that Custom Field of Issue Age using Automation.

I would like to have a Column In Issue Navigator & Dashboard where I can see the Turn Around Time : (Resolved Date - Created Date ) 

Turn Around Time Mentioned in Hours: Mins: Sec

Turn Around Time Mentioned in Days

 Regards,

Swaroop

[Sachin Dhamale · Accepted solution]

@Swaroop Bangera

You can create a new custom field called a Issue age and then through automation you can calculate the average age of an issue as per your formula and then update to that custom field

then you can display that custom field on dashboard gadget and issue navigator.

OR You can you script runner plugin where you have scripted field and through script you can calculate the age of an issue and display in that scripted field.

[Swaroop Bangera]

one more query I had is

@Sachin Dhamale  @John Funk  So in some projects the Rule gets Throttled where it only updates the First 1000 issues.

I want the rule to run on the remaining issues as well.

What do you suggest in such cases where I have more than 1000 issues for the rule to run?

[Swaroop Bangera]

Thank you @John Funk@Sachin Dhamale for your responses

So in the Trigger Section there was check mark to tick , to run the rule on issue which have changed and it seems that was ON.

I have turned that off and run the rule again. And its working. Will check tomm again if its working properly.

[Emre Toptancı _OBSS_]

Hello @Swaroop Bangera

If you are OK with using a marketplace app for this, 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. This is the most flexible way to get time reports based on your issue workflows.

   

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 Vertical 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

[Swaroop Bangera]

Hi @John Funk & @Sachin Dhamale I am trying to created a custom field and need help in formula for Filled which will be fetched by Automation.

I need 2 Custom Fields , while creating new field I have selected type as Number.

1. Issue Aging:  Today's Date - Issue Created Date

2. Turn Around Time : Issue Resolved Date - Issue Created Date

I have created Issue Aging Custom Field by Adding {{now.diff(issue.created).abs.days}}

However I see the value fetched is 1 day less. For eg. If Issue Created date is 26 May 2023 & Today's Date is 29 May 2023. Its shows 3.

Similar Result for TAT as well. I have used {{issue.resolved.diff(created).days}}

I help with the formula for both the results.

[Sachin Dhamale]

@Swaroop Bangera

refer this 

try to remove abs parameter or try to add it at the end {{now.diff(issue.created).days.abs}}

It might be not considering today date because its today day is not finish. If you want to consider today days ad well then you can add 1 in that smart value

[John Funk]

Hi Swaroop - thank you for your kind works about the Community, and I am glad you find it helpful. 

Columns in a board relate to Statuses in your workflow. So you can't have a column on a board that shows the custom field information alone. However, if you are using a Company-managed project, you can add the custom field to the card so that it shows on the board. 

Click the 3 dots menu on the board in the upper right and select Board Settings and then Card layout. Add your field there. 

[John Funk]

Well, that formula seems correct to me - 29-26 is 3. What are you expecting to see there and why? 

[Swaroop Bangera]

My bad John , you are correct. I was considering it to calculate the present day as well.

[Swaroop Bangera]

Hi, am not able to judge which am getting the Issue Age different, in same Created Dates here.

Kindly check the attached image.

The rule I have used is as mentioned by @Sachin Dhamale {{now.diff(issue.created).days.abs}}

[Swaroop Bangera]

how does a day older 25th may Should 3 days as Issue ageing and 26 may Shows 4

[Sachin Dhamale]

@Swaroop Bangera , Can you check the time as well and see the difference between two dates

[Swaroop Bangera]

So the first (Highlighted) 26th May Ticket, the time is 26th May, 4:00 PM

the second (highlighted ) 26th May Ticket, the time is 26 th May, 3.14 PM

Still the older Date of 25th May, 5.17 PM , it shows 3 days

[John Funk]

What triggers this rule?

[Swaroop Bangera]

I have Scheduled it to run daily at a specific time. 

[Swaroop Bangera]

Some more examples with similar Dates

[John Funk]

Well, if it runs everyday, and the rule use {{now}} that value will change every day.