Hello
How is time in control chart calculated? If I have 3 columns out of the 5 selected
Thanks
Hello @steliosavramidis,
Control Chart gives limited details about its inner workings and offers limited flexibility for reporting.
If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for similar needs. It is available for Jira Server, Cloud, and Data Center.
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.
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.
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. 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:
Timepiece - Time in Status for Jira
EmreT
Hi @steliosavramidis welcome to the Atlassian community.
Given here the full details about reading a control chart.
And few ways you could use a Control Chart:
Analyze your team's past performance in a retrospective,
Measure the effect of a process change on your team's productivity,
Provide external stakeholders with visibility of your team's performance, and
For Kanban, use past performance to set targets for your team.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi there. I have already read that page. It doesn't clarify. Thanks.
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.