Problems with control chart (BUG) - issues not closed been exhibited

Question

According to my understanding, a control chart should only exihbit issues that are already closed.

If it´s not closed, does not make sense to plot the results and contribute to lead times calculations.

Here is an example of a controlchart of one of my projects. Notice the round squared dot1.png

When I click on it, I see that there are 2 issues that are contributing to this computation

2.png

3.png

In portuguese, Fechada means "Closed"  and Priorizada means "Priorized". I expect that only the Closed issues would be showed in this graph.

I know that I can solve this putting a quick filter that only considers closed issues. But I think it´s not necessary, because by definition, Control Charts have plots of issues closed.

As far as I can remember, the previous versions of the control chart dealed correctly with this issue.

Anyway, my JIRA version is: v6.0.8, so it´s possible that this problem is already corrected in recent versions.

Regards.

1.png

2.png

3.png

William McNelis · Answer

That's got it sorted!  Thank you, Annie!!!

Annie Ioceva _Nemetschek Bulgaria_ · Answer

Hello,

I ran into the same problem and I found the answer! This is how currently the Control Chart works, see the docs:

Tip 3: Exclude current work

The Control Chart shows data for issues that have been in a selected column, but are no longer in a selected column. This gives the cycle time (total elapsed time) for the issues. However, by default, this will include issues that are still moving across the board.

To view the data for completed work only in your Control Chart, create a Quick Filter with this JQL: status in (Resolved, Closed). Configure your Control Chart to use this Quick Filter.

In case this is a problem for you, vote for this Bug to be fixed - https://jira.atlassian.com/browse/JSWSERVER-12122

Cheers,

Annie

Will McNelis · Answer

Just giving this a bump as I am experiencing the same, and cannot work out why.  Seems there are a few people who have experienced this, but I have yet to find a reason or answer...