I need a filter in JQL that allows me to track the time to solve task

[Diana Cabrejo]

I need to track the time it takes for a developer to solve a task.
Somebody could help me?
Thank you.

[Trudy Claspill · Accepted solution]

How do you define the "time it takes a developer to solve a task"? Are you basing it on the date an issue is created vs. the date it is resolved? Are you basing it on the time between some statuses? Are you basing it on the logged against the issue?

And what do you mean be a filter to get this? A filter gets you a set of issues. Are you wanting to filter based on the "time it takes a developer to solve a task" or are you wanting to generate a report of how long it took for tasks to be resolved?

[Diana Cabrejo]

Maybe the date from when the task goes In Progress to when it is solved.

I would like to know if there is a filter based on the time it takes a developer to solve a task, but in a specific period, since in reports I find an option to visualize the workload of each Dev but since the project started and I need it for a period of 15 days

[Trudy Claspill]

Jira does not natively provide that type of reporting for Software projects.

You would need to create a custom field to record the date that the issue transitions to the "start the clock" status. You could set that field through an Automation rule.

You could then either generate a report that includes that custom date field and the Resolved Date field, and do the calculation manually, or you could create another custom field to record that calculated value and use another Automation rule to set it when the issue transitions to the "solved" status.

When you are looking to get the data for a specific time period, you are also going to have to decide what dates in the issues have to be within that time period. Do both the start and finish date have to be in that time period, so that you are only looking at the issues started and finished within the time period? What if the work starts before the time period, but finishes during the time period? What if the work starts during the time period but doesn't finish in the same time period?

Alternately you can search the Marketplace for an app that extends the JIRA functionality to provide you with a report like that.

[Diana Cabrejo]

Thanks is a good tip

[Trudy Claspill]

There is also a native Resolution Time gadget for the JIRA Dashboard, which works for Software projects, but you are limited on customizing the time period reported on, and I don't know if you can customize which statuses it considers as the starting and ending of the calculation.

[Diana Cabrejo]

Thanks sir, that option works for me. 

[Emre Toptancı _OBSS_]

Hello @Diana Cabrejo

This is not something Jira provides out of the box. You can set up something manually using automation rules and/or custom fields but that needs to be repeated for each status. This will be hard to maintain. 

The Jira Resolution Time reports or gadgets seem to provide this data but please note that they only show "Resolved" issues. Non-resolved ones are excluded from the charts, which is misleading.

For a ready-built solution that offers great flexibility and details, our team at OBSS built Timepiece - Time in Status for Jira 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, Resolution Time, Cycle Time, or Lead Time. For example, you can add a column to the report that includes all statuses in your workflow (except resolved and closed) and see the total time between creation and resolution of the issue.

You can calculate averages and sums of those durations grouped by the issue fields you select. (For example, see the total InProgress time per Epic or average Resolution Time per issue type). 

Below are screenshots that show a custom Lead Time field that shows the total of ToDo and InProgress statuses. The same can be done for any status combination.

  

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.

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

Timepiece - Time in Status for Jira

EmreT

[Diana Cabrejo]

Thank you very much, your answer and explanation are very good.

[Mehmet A _Bloompeak_]

Hi @Diana Cabrejo ,

As an alternative, you can try Status Time app developed by our team. It provides reports on how much time passed in each status as well as status entry dates and status transition count.

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). And all these are available as gadgets on the dashboard too.

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

If you are looking for a free solution, you can try the limited version Status Time Free. Hope it helps.