Issue status different in GreenHopper

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?

6 answers

1 accepted

0 votes

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.

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.


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.

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.


I stand corrected, but my question is why isn't "Resolved" considered completed? Does it have to be closed to be considered completed?

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).


Maybee its the mapping, in rapid configuration you map your JIRA statuses to columns in Scrumboard.

I thought about that also, but it is not the case as the statuses are tied directly to the issue status in the report.

Does the closed JIRA issue in your example have a resolution, or is it Unresolved?

The issue has a "Fixed" resolution.

So far no updates. Anybody have any other suggestions?

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,975 views 12 18
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot