How to set Resolution time for Business Project ?

[Laura Orlovic]

I'm trying to collect information about time between moment the issue was created to when it wad solved for a business project.

Is it something that is not doable through the resolution report? I have access to it but marking issues as Done as workflow status doesn't change them to Resolved.

Is there a potential workaround? ie. an automation that would fill out a time stamp custom field with the SLA that we can then compare on a report with the due date?

Is it due to the fact we're using business project? What types of project cn we use to get this report?

Thanks a lot,

Laura

[Mariana_Pryshliak_Saasjet]

Hello @Laura Orlovic 

I recommend you to try Time in Status for Jira Cloud. It helps to get the Issue Age data (from creating to solving).

You can see the data you need in the Total time column shows how long it takes to complete each issue.

It also generates 7 types of status time reports, including a Time in Status one, that tracks how much time has been spent in each status.

It's developed by my team and is free for using up to 10 users. Please, let me know if you have any questions.

[Rahul_RVS_Support]

Hi @Laura Orlovic 

Welcome to the community !!!

If you are fine with a marketplace app, you can try out our add-on to get this data.

Time in Status Reports 

 You can set your own resolution time by grouping your statuses.

The main features of the app are as below

• Multiple Time in Status Reports. Excel Export available for all status reports.
  
  • Time in Status
  • Time with Assignee
  • Time in Status with Assignee
  • Time with Assignee per Status
  • Status/Assignee Count
  • Multiple Transition Reports
  • Avg Time in status reports
  • Status Transition Dates Report
  • Time in Status Per Time Grain
  • Time with Assignee Per Time Grain
• Status grouping
• Save your reports
• CSV Export
• Multiple chart types
• Dashboard Gadget

[Emre Toptancı [OBSS]]

Hello @Laura Orlovic

If you are OK with using a marketplace app for this, our team at OBSS built Time in Status 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 and on each assignee.

       

Time in Status also has Duration Between Statuses report type which shows the duration from issue creation to a specific status or the duration between two specific statuses.

  

The app has Consolidated Columns feature. This feature allows you to combine the duration for multiple statuses into a single column and exclude unwanted ones. It is the most flexible way to get any measurement you might want. Measurements 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 (organization) 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.

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.

And the app has a REST API so you can get the reports from Jira UI or via REST.

  

Using Time in Status you can:

• See how much time each issue spent on each status, assignee, user group and also see dates of status transitions.
• Calculate averages and sums of those durations grouped by issue fields you select. (For example, see average InProgress time per project and per issue type.)
• Export your data as XLS, XLSX, or CSV.
• Access data via REST API. (for integrations)
• Visualize data with various chart types.
• See Time in Status reports on Jira Dashboard gadgets

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

EmreT

[Stephen Wright _Elabor8_]

Hi @Laura Orlovic 

Are you using Cloud? And using a Jira Work Management project?

If yes, there is a bug where the resolution field (and therefore, resolution date) are not set in this project type - see JWMCLOUD-180 for more details.

There are a few options...

---

 Custom Fields + Automation

• Create two Custom Fields:
  • Date Picker: For example, Done Date. You could alternatively create a Date/Time Picker if the hours/minutes are useful.
  • Number/Text Field: For example, Lead Time. To house the days/time difference between creation and closure
• Use Automation to...
  • Populate the "Done Date" when the Issue is transition to Done
  • Calculate the "Lead Time" and populate it into a field

---

Software Project + Automation

• Use a Software Project type instead - so the Resolution Date populates
• Then, you could still create the "Lead Time" field, and use Automation to populate it

---

I think it's easier to do for "days inbetween" rather than hours or minutes, as it's a whole number.

You could also not do the "Lead Time" automation - and just collect the date data, using it elsewhere to calculate lead time (eg. exported to Excel).

Let us know if either of these options work for you - or, if you need more specific instructions to make this work!

Ste