In the Control Chart, if there is an individual story, I can click on it and see the time spent in each stage. But for a cluster I dont see those same details. How do I see that?
Hi
You can also try out
Agile Tools : Epic Tree & Time in Status
The add-on provides the time spent in each status for the entire lifecycle of the issue. You can also extract the transitions history of the issue. Along with various Issue stats reports, you get additional features like Epic Hierarchy & Links Hierarchy to track the project's progress. The main features are as below
Hi @James Phillips ,
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 by any field(eg. average in progress time by project, average cycle time by issue creation month). 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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you're open to using third-party apps, check out Time in Status for Jira Cloud. It's a top-rated time monitoring app developed by my team. You can generate 7 types of reports here.
All reports are available as Grid and as Charts (Pie, Bar, and Area).
Let me know if you have any questions.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @James Phillips
That is one of the limitations of the built-in Control Chart. It will show you durations but it won't show individual issues. Plus, you can't get its raw data. It is more aimed towards seeing the big picture.
In case you are OK with using a marketplace app, 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.
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).
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.
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.
Using Time in Status you can:
Timepiece - Time in Status for Jira
EmreT
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yup, that is definitely a limitation of the built-in, Jira interpretation of a control chart. And, you may only zoom in so far on the timescale and that may not be enough to separate them. Here is a suggestion to improve that effect: https://jira.atlassian.com/browse/JSWCLOUD-16665
One cumbersome work-around is to select the link to "View in Issue Navigator", pick one or more of the keys, and create a quick filter for them on the board. On the report you may select the quick filter to isolate them.
This effect is caused by batch completion, or moving things in bulk on a board. If that regularly happens and is normal for the team, consider investigating marketplace addon reports/dashboard gadgets which provide better access to the data. Or, consider using automation for Jira and custom fields to hand-build the data capture.
Best regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.