Got a weird one for you - I've recently changed the workflow some of our projects used (as a phased roll out).
It now has completely different statuses to what we used before and all seems to working well. Apart from one thing - the Velocity charts now have no 'Completed' count for any of the previous sprints (see below).
Any idea what's wrong here? All the issues that have been completed have the correct status (Done) and a resolution. The status of 'Done' is mapped to the last column in the rapidboard and I'm using a form of the simplified workflow so there is technically no 'end state' defined by steps in the workflow.
Greenhopper V6.2.2, JIRA V5.2
I guess it won't work. The reason being, when GH looks at the history of the issue on the day of Sprint completion, the status of the issue was the old status.
Only when you changed the workflow, all of them changed to the new status as part of the workflow migration procedure, am I right? (you can also check this in the history tab of an issue)
Happened to us too. Apparently the "problem" could be that the REPORT view is not taking the new FINAL STATUS into consideration.
So the velocity is gone because to Jira's eyes, because the points delivered (which happens when an issue gets to its final status) are not delivered anymore (they are not in the final status anymore (because you changed your workflow). So this leads me to think that the report view is reading the status from the DB every time you pull the velocity report (that's why it realized the is no longer in the old workflow status) but is not updating what is the final status for the current workflow, and therefore unable to see that this new status is still a final status and therefor the issue (and its points) were delivered in that sprint.
In a few words, the query seems to realize of the status change of the issue, but does not realize that this new status is also the final status of the current workflow (and so, the issue should still be considered delivered, and those points accomplished).
IF my diagnose is correct, I think the query in that page should be updated by Atlassian to take this into account.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs