Control chart

[Tata Tatkhashvili]

Hi there

in which cases can't use control chart? I guess the problem is that, tasks /  issues have not defined start date and due date. could you help me ?

thanks a lot

[Trudy Claspill]

Hello @Tata Tatkhashvili 

The Control Chart does not depend on Start Date or Due Date fields. Refer to 

https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-control-chart/

The Chart is based on the time spent in statuses.

[Tata Tatkhashvili]

Thanks for your feedback. Unfortunately I don't know why it doesn't work. 

[Trudy Claspill]

Hello @Tata Tatkhashvili 

Please provide more information.

Can you provide an image of the chart?

Can you tells us the parameters that you have set on the chart?

Can you explain what you mean by "it doesn't work"?

Can you provide the details of an issue that you think should be represented on the chart but is not?

Without more information we cannot provide more specific help.

The parameters you set can affect what displays in the chart. If issues are not changing statuses that will also affect what displays in the chart. The chart is based on the statuses of the issues changing, not on Start Date or Due Date fields.

[Mehmet A _Bloompeak_]

Hi @Tata Tatkhashvili

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.

Note: If you are interested in cycle and lead time, you can have a look at the article below.

Cycle Time and Lead Time in Jira: Productivity Measurement with Two Critical Parameters

Hope it helps.

[Emre Toptancı _OBSS_]

Hello @Tata Tatkhashvili

If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this need. Time in Status provides a much more detailed, transparent, and flexible solution compared to the standard Control Chart.  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