Control chart report number of issues does not match with the actual count of issues

[Torres, Rodolfo (R.)]

I´m looking at a control chart report from a board in JIRA and from a total of 200+ issues I´m only looking at around 95+ issues in the report
Do you know why this is happening or the reason of it not reporting the status of the whole sample?

[Mehmet A _Bloompeak_]

Hi @Torres, Rodolfo (R.)

As an alternative, 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.

[Emre Toptancı _OBSS_]

Hello @Torres, Rodolfo (R.) 

Jira's own Control Chart offers limited details and flexibility. In order to get more details, you'll need to check each issue's history independently. If you want to get better reports with more flexibility and details, I suggest you use a marketplace app.

If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. 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:

• See how much time each issue spent on each status, assignee, user group and also see dates of status transitions.
• Calculate averages and sums of those durations grouped by issue fields you select. (For example, see average InProgress time per project and per issue type.)
• Export your data as XLS, XLSX, or CSV.
• Access data via REST API. (for integrations)
• Visualize data with various chart types.
• See Time in Status reports on Jira Dashboard gadgets

Timepiece - Time in Status for Jira

EmreT

[Ravi Sagar _Sparxsys_]

Hi @Torres, Rodolfo (R.) 

Check Time scale, Refine report (Columns, Quickl Filters).

Ravi

[Torres, Rodolfo (R.)]

Hi Ravi Sagar _Sparxsys

To my understanding, if I select a colum it shows me the amount of issues that were in that state and the amount of time according to the timeframe I selected, right?

[Torres, Rodolfo (R.)]

And another thing I´m looking is that the report is showing a lot more average time than the highest time in the chart. Also saying that the max time is more than two thousand weeks, even though the first issue was created less than a year ago.

[Bill Sheboy]

Hi @Torres, Rodolfo (R.) -- Welcome to the Atlassian Community!

As @Ravi Sagar _Sparxsys_ noted, the settings and actual issue history are key in understanding the display of Atlassian's interpretation of a "control chart".

For your outliers, I recommend opening up those specific issues and looking at the history.  From what you show in the image, there are several issues indicating between 18-20,000 days.  Take a look at those first.

Kind regards,
Bill

[Lucy Dilts]

@Ravi Sagar _Sparxsys_  Interested in your findings, if you would be willing to share.

Best.

Lucy