According to this Atlassian post, the control chart for Next Gen will be added some time in 2020:
@Amir Barkal, i do not think you will get an estimate in this forum. Short of seeing an Atlassian convey that 'we are working on this now' or 'this is on our roadmap', I have never seem any commitment for feature schedule in the Community. Nor would I expect one TBH.
The classic project "control chart" has some limitations in regards to being an actual and useful control chart for process evaluation. If that same version is implemented for NextGen, it may have the same limitations.
Please consider reviewing the documentation for the current chart to see if it meets your needs, and if not, consider checking the marketplace for dashboard gadget options or using a data export/pull to build your own analytics.
Hello @Will McNelis ,
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 as well as entry/exit dates for all statuses. 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 and counts grouped by issue fields you select. (For example see the total InProgress time per Epic, or average number of InProgress transitions 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 which means you can 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:
Hi @Will McNelis -- Welcome to the Atlassian Community!
If you do not want to purchase an add-on from the marketplace for lead and cycle time, you have several options:
Thank you both @bill and @Emre Toptancı _OBSS_ for the responses! Emre, I will check out the add on that your team built for sure. Bill, I was already thinking about biting the bullet and doing something in Power BI as the control chart always did leave a bit to be desired.
As a side note, it is strange that Atlassian would leave the tool out that provided industry standard metrics out of the box with no replacement. Oh well...
Hi @Will McNelis ,
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.
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events