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
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.
I also experience this problem. I am using JIRA 6.3.
I would like to be provided with option to only look at Stories that are "CLOSED" and then visualise their cycle time.
Keeping the exiting feature of viewing cycle time through different phases in the board is also useful for me when you get down to the nitty gritty of see why issues are taling so log to close or what certain items have really fast cycle times.
Anyways, I would like the feature to have option of only viewing CLOSED issues.
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG