One of our groups is using a SCRUM board in GreenHopper. While looking at the Sprint Report, we noticed that the issue statuses in GreenHopper are different from what they actually are in JIRA. For example, there is a closed JIRA issue, but it is appearing as "In Progress".
Does anyone know what's going on?
Hi Caesar,
It could be caused by a few reason, at first I'm suspecting this might be due to the Column mapping in Rapid Board. Could you verify what are the status mapped under the right most column? Could you provide a screenshot of your Column mapping for us to verify?
Furhermore, this might be the case with Indexing problem, thus could you please Re-Index your JIRA instance and see if there is a change in the report?
Hope this helps.
Cheers, Vicky
I've reindexed already and that didn't resolve the issue. In regards to the column mapping, that shouldn't matter as I'm working with a velocity report on a Scrum board. The velocity report shows the actual issue status. That is what is incorrect. The issue is closed but in the velocity report, it is showing as resolved.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are you sure you're in the velocity report? That report just shows a sum of committed vs completed. Maybe attach a screenshot of your issue in the board and in JIRA view issue.
Thanks,
Shaun
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am positive that I am in the velocity report. I can only attach a partial screen shot due to security policies. This is in the "Issues Not Completed" chart. The issue on the bottom marked "Resolved" is actually closed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's not the Velocity chart, it's the Sprint Report.
The Sprint Report shows the status of the item at the end of the sprint if the sprint is completed.
Thanks,
Shaun
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I stand corrected, but my question is why isn't "Resolved" considered completed? Does it have to be closed to be considered completed?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The issue needs to be in the last column of the board to be considered completed (i.e. you need to mapped the Resolved state to the last column).
Thanks,
Shaun
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So far no updates. Anybody have any other suggestions?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Does the closed JIRA issue in your example have a resolution, or is it Unresolved?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I thought about that also, but it is not the case as the statuses are tied directly to the issue status in the report.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Maybee its the mapping, in rapid configuration you map your JIRA statuses to columns in Scrumboard.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Atlassian Government Cloud has achieved FedRAMP Authorization at the Moderate level! Join our webinar to learn how you can accelerate mission success and move work forward faster in cloud, all while ensuring your critical data is secure.
Register NowOnline forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.