Graph for time spent on issue from issue opening in dashboard

[Akim Boukhelif]

Hello everyone,

One of my colleagues is managing multiple projects and would like to highlight context switches between all those projects.
He created a dashboard to count number of issues but ideally he would like to display on a graph the time spent on issues from issue opening. 
Here's how it could look like:

• On the left: Number of issues
• On the right: Graph for time between specific dates in a table (or the same table). 

Could you please help with this?

Thanks,

Akim

[Diogo Teles · Accepted solution]

Hi @Akim Boukhelif 

Jira has powerful reporting features, especially if you work within the Agile framework. It is impossible to cover all use cases, although time in status is a very popular requirement and the other answers already mentioned some brilliant add-ons for this. 

If you are looking for a solution that does not involve an increased cost, then you will likely have to go down the path of integration.

REST API gives you lots of options for this (not for the reporting itself, but you could use it to create  middleware or other tools to meet requirements). However, I'll focus on a no-code approach below.

For example, if you can work with Google Sheets, you can use the free Jira Cloud for Sheet (official) add-on by Atlassian to extract Jira Cloud data into a Google Sheet.

Alternatively, if you use Excel, you can use Jira Cloud for Excel (Official)

This add-on can be set up in a way that the data gets updated automatically. There are a few different data sources you can use. The most straightforward is a Jira filter. However, you can also write a JQL query in the add-on and use the results as data source, or use it as a function within the sheet. 

Additionally, you can extract data from fields that are not easily accessible via JQL, like transition dates and transition authors.

If you are able to adopt this type of solution, then you now have all the flexibility of a spreadsheet to create your reports. 

This will open up multiple approaches to your requirements. You can use transition dates to calculate the time in status. Alternatively, you could use a combination of automation and custom fields in your project to log milestone dates into your issues (increases admin overhead but makes data processing easier) and then use those for reporting. Or use whatever approach your creativity and spreadsheet skills lead you to.

To display your reports to stakeholders, you can create a sheet within the workbook to act as a dashboard (remove grid, place your graphs in a tidy manner etc) and then publish that sheet.

Furthermore, you can use your published link to present the dashboard (or individual reports) using an iframe on a Confluence page. This will allow you to have Confluence pages with live custom reports.

Being able to extract Jira data into a workbook gives you a world of options. As long as you can work with all the tools involved and are mindful of security when publishing the reports. For example, I had a situation where the Org was still running a version of Excel incompatible with the Addon and use of Google Workspace was not allowed. That scenario limits this option a lot.

NOTE: There was an end-of-life announcement for Jira Cloud for Sheets last year, but it was revoked shortly after. You can read about it here. 

I hope this helps. If you do find a better solution without using paid add-ons please do share, it would be most welcome!   

[Akim Boukhelif]

Thanks, it seems our company are using Timesheet as an add-on, and it seemed to fit the bill for my colleague.
Thanks for the Google Sheet add-on, I'm keen to try it out for myself.

[RVS_Support]

Hi @Akim Boukhelif 

If you are open for a mktplace add-on, you can try our addon:

Time in Status Reports 

The add-on provides the time in status for the complete lifecycle of the issues.

Do try it out.

Disclaimer : I work for RVS, the vendor for this app

[Valeriia_Havrylenko_SaaSJet]

Hi @Akim Boukhelif  👋

As an alternative , I guess you can try Time in Status for Jira Cloud. 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," and provide 7 types of reports to help you identify areas for improvement. Add-on developed by my team.

Also Time Between Statuses will be an option for you too. This add-on, which measures connections in the workflow, through a transition time in specific issues. You can count Cycle and Lead Time by setting start/stop and pause statuses in the configuration manager. To detail the calculation conditions you should select the first/last transition to/from status. This add-on also developed by my team.

Add-ons have a 30-day free trial version and free up to 10 users. 
Please, let me know if you have any questions

Hope it helps 😌
Valeriia

[Anthony Morais]

Hi @Akim Boukhelif 

Let's go
I recommend installing this app to count the time spent in each status.

After installed, Go to Dashboards > Create Dashboard

Name and configure who can edit and view.

On the right side under "Add a Gadget" type Time in status and choose as shown in the image

 

Configure as below and scroll down and click Save.

To the other frame.
Create a filter with this JQL: project = Your project AND statusCategory != Done

Go to Add a gadget and choose "Filter Results"

Choose Saved filter

The result would be this:

I hope it helps!

If so, mark it as accepted answer!

Regards,

Anthony

[Akim Boukhelif]

Thanks, but I'd rather do it without installing any additional apps.

[Anthony Morais]

Hi @Akim Boukhelif 

Ok, could you then just mark it as an accepted alternative answer?

Thanks!

[Dan -minware-]

Hey @Akim Boukhelif -

If you are open to working with a 3rd party we can help with this at minware. 

Below you can see an expanded view of our Flow Efficiency report. The top row is an aggregate view of the epics below and if you "follow the blue" from left to right you can see that towards the end of this sprint we had poor Cam switching back and forth between 5 different tasks in one day - yikes!

This ultimately turned out to be some technical debt that we needed to get a handle on - being able to visualize the context switching in this way made it crystal clear we needed to prioritize that change. 

We offer a free trial - let me know if you want to check it out!

Dan