nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

What's the "correct" way to manage outliers in the Control Chart caused by other teams?

Michael E_vhi45s

So long story short is that we have a long backlog of low prio bugs that have just been sitting.

Now they're slowly getting delegated to teams, as we are catching up.

But as a result our teams are seeing these huge spikes in outliers in the Control Chart, through no fault of their own.

How do we handle these in the best way to avoid having outliers that do not represent the teams?

Accepted answers

Alex Hoogendoorn

@Michael E Hi, here's a jira article on how to exclude outliers: https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-control-chart/.

I hope this will help you. It may not be the prettiest way of excluding outliers, but it will work - like using any other quick filter.

Cheers

All comments

Emre Toptancı [OBSS]

Hello @Michael E

I don't have anything that will make Control Chart show the correct values but I can recommend the Timepiece - Time in Status for Jira app built by my team at OBSS which has two features that might help you.

In summary, Time in Status allows you to see how much time each issue spent on each status. The app also can draw charts based on this data.

tisCloud_StatusDuration_LeadTime_with Estimates.png

The first feature useful for you is the 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. If your ancient bugs were sitting in some kind of "Waiting" status, you can exclude this status from your measurements.

The second one is the Date Trimming feature. This feature allows you to get reports on a given time window (instead of the whole issue history). If your team started working on these bugs at the beginning of this month, you can trim their histories to get a report that starts there. It will be as if the issues started to exist on the given date.

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. (Filter and Sort options are even available here.)

tisCloud_StatusDuration_LeadTime_Average_TimeGrouped.png

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 for Jira Cloud.

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.

Timepiece - Time in Status for Jira

EmreT

Mehmet A _Bloompeak_

Hi @Michael E

Welcome to Atlassian Community!

If you prefer to use a marketplace app, 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.

This app has a dynamic status grouping feature so that you can generate various valuable reports as time in status, time in assignee, status entry dates and status counts, cycle time and lead time, average/sum reports by any field(e.g. average in progress time by project, average cycle time by issue creation month).

You can search issues by Project, Issue Type, Status, Assignee, Issue Creation/Resolution Date(and any other Date field) and JQL Query.
Status durations are calculated according to the working calendar you define. 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.
You can set different duration formats.
You can export reports in CSV file format and open them in MS Excel.
You can also add this app as a gadget to your Jira dashboards and reach “Status Time” from Issue Detail page.
You can enable/disable access to Status Time reports&gadgets and Issue Detail page per project, users, groups or project role.

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

Hope it helps.

Valeriia_Havrylenko_SaaSJet

Hello @Michael E 👋
Welcome to Atlassian Community!

As an alternative, you can try Time in Status for Jira Cloud developed by my SaaSJet team.

Time in Status for Jira Cloud can help track and analyze your team performance metrics easily, including how much time your team members spend on different tasks and how much time is spent in different workflow stages. You can also export data to CSV and XLSX files for further analysis or share reports with third-party analytical systems.

GIF TIS.gif

hope you find it helpful 😌

Michael E_vhi45s

No help, only people trying to sell their apps...

Alex Hoogendoorn

@Michael E Hi, here's a jira article on how to exclude outliers: https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-control-chart/.

I hope this will help you. It may not be the prettiest way of excluding outliers, but it will work - like using any other quick filter.

Cheers

Michael E_vhi45s

Thank you Alex!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud