Options for data tracking - time to completion since "request date", time "in progress", etc

[taylor.roberts]

I am having a hard time with figuring out filters. I want to become more knowledgeable on how to read my data and workflow. Here some things I need to know from my board: 

1. Time (days) to completion since request date 

2. Is there a way to remove weekends from data tracking/time to completion? 

3. How long a ticket has been "in progress" or stuck in one column (hr & min) 

Some insight - my board is used to track work completed on support tickets. I need to see the productivity in #s for my team so that I can better understand where the most of our time is being taken AND so that I can set attainable goals. Any other recommendations for this type of workflow would be greatly appreciated! 

[Mariana_Pryshliak_Saasjet]

Hello @taylor.roberts 

You can try Time in Status for Jira Cloud add-on, which shows how long an issue has been spent in each status, and generate a report. So you can monitor how long a ticket has been "in progress" or stuck in one column easily! And get detailed data on time from the requested date to completion.

You can also exclude non-working days and holidays from the calculation using "Calendars" (Multicalendar function). Just choose working days and choose those which are non-working.

I hope you find it helpful

Best regards, Mariana

[Bloompeak Support]

Hi @taylor.roberts ,

There is no such report available inside Jira by default. You can use Jira REST api to get the raw data, parse the json data and calculate one by one for each issue. You need to make development for the above steps.

Or you can search for a marketplace app which does all the above for you. At Bloompeak, we developed Status Time app for this exact need.

It provides reports on how much time spent in each status as well as status entry dates and status transition count. Report can be exported as CSV, so that you can use external tools like Microsoft Excel or Google Spreadsheet to process the exported data.

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. It has various other reports like assignee time, status entry dates, average/sum reports(eg. average in progress time per project).

Here is the online demo link, you can see it in action and try. Hope it helps.

[Emre Toptancı _OBSS_]

Hello @taylor.roberts ,

If you are using Jira Software, Control chart in Kanban Board reports offer some visibility into this. It works with board columns rather that individual statuses and shows issues in a grouped chart rather than as individual issues. Custom calendar support is also limited but it can help you to get a high level report.

Alternatively, you need to do your own custom development. Since you are on cloud, you can't access the database so the option for you to get issue history data will be through REST API.

Beyond that, you can use a marketplace app to get the report you need.

For a ready built solution that offers great flexibility and details, our team at OBSS built Time in Status app for this exact need. It is available for Jira Server, Cloud and Data Center.

Time in Status allows you to see how much time each issue spent on each status or assigned to each assignee. You can also combine statuses into consolidated columns to see metrics like Ticket Age, Cycle Time or Lead Time. You can calculate averages and sums of those durations grouped by issue fields you select. (For example see the total InProgress time per Epic, or average Cycle Time per issuetype). 

    

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.

The app has Custom calendar support that your are looking for. This feature enables you to get your reports based on a 24/7 calendar or your custom business calendar. (This one is important because a 24/7 calendar in most cases shows misleading data. For example an issue created at 16:00 on Friday and was resolved at 09:00 on next Monday seems to stay open for 2,5 days but in terms of business hours, it is only a few hours. You can see this using Time in Status by OBSS.)

Finally, the app has History Trim feature. This feature allows you to report on a subsection of issue histories instead of the whole history. Very useful when you want to focus on changes made during sprint or project phase.

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 issuetype.)
• 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 (released for cloud, server&DC gadget coming soon)

https://marketplace.atlassian.com/1211756

EmreT