I'd like to potentially visualize how onboarding is going by tracking the amount of time it takes new employees to complete their Nth ticket.
I want to map this data with a jira dashboard widget where the x-axis represents the average on that day (time span 30 days?)and the y-axis to represents the average time it takes for engineers to resolve their Nth ticket.
Is there a way to do this with Jira advanced search, the Enhanced Search plug-in, and stock Jira dashboard widgets?
Hi @Jay Henry
If you're ok with the third-party add-ons, you can get such data easily with Time in Status for Jira Cloud developed by team.The add-on generates 7 types of reports, including the Time in Status and Assignee time reports. So you can track how long it takes each assignee to complete each ticket. Also, it can be displayed as Chart or Graph (according to your needs).
Hope it helps
Hi @Jay Henry
Welcome to Atlassian Community!
You can try Status Time Reports app developed by our team. It mainly provides reports and gadgets based on how much time passed in each status.
Here is the online demo link, you can see it in action and try without installing the app.
If you are looking for a free solution, you can try the limited version Status Time Free.
Note: If you are interested in cycle and lead time, you can have a look at the article below.
Hope it helps.
Hello @Jay Henry ,
This is an interesting question with a not so easy answer. But I think I can offer something that might help.
First, the JQL language is used for searching among issues. It is capable for filtering the issues in the resultset. But it can't perform operations on those issues. Getting the Nth issue is one such case. JQL doesn't have the concept of "Nth issue".
Taking one step back, I see that you want to see the improvement of an employee over time. For that one, I can offer a solution but it will require a marketplace app.
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.
Before getting to the details of your case, let me tell you what Time in Status does.
Time in Status mainly allows you to see how much time each issue spent on each status and on each assignee.
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.
As an alternative approach, Time in Status also has Duration Between Statuses report type which shows the duration between two specific statuses.
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.
This is where it gets interesting for you. If you group your issues by assignee and some date parts, you can get a report where it will show you the metrics for an employee over time. (The report below is based on test data but it will give you the idea). You can get down to hour resolution with that.
I guess this one will help you see the trend over time. You can even segment this report using other issue field values.
Time in Status 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: