Connecting sprints in GreenHopper and release versions

We are using the GreenHopper plugin for Agile. We added our backlog tasks, created a sprint, added subtasks and started the sprint. When we go to the Agile Reporting tab, the burndown looks correct.

However, I cannot get this to show up in any of the dashboard burndown widgets. They mostly seem to work off of ‘versions’, but the Greenhopper Agile screen works off of ‘sprints’. I don’t see a way to connect sprints and versions.

Any tricks you needed to do for this?

3 answers

1 accepted

1 vote
Accepted answer

We're enountering similar issues. Here's what we've done.

Assign all issues in a sprint to the appropriate fixversion

Go to the Classic Board for the project(s) associated with those versions. Update the start and end date for the applicable versions there (that is the only place these attributes exist). Configure the classic board for the project(s) to map the statuses to the appropriate To Do, In Progress, and Done columns.

Then, use the Agile Gadget and set it up for the applicable project. That way, you can use it to show burn up, burn down, and story points by version.

If Greenhopper added these attributes to the JIRA version management and created an admin UI to map statuses to To Do, In Progress, and Done, then these gadgets can still work without the classic boards. I don't see harm in giving users the ability to configure the statuses for a version in order to use the stop light progress bar as it doesn't have to match columns and status mapping in rapid boards. Plus, you cannot use Greenhopper without Jira; adding these attributes to JIRA version management only makes it easier to have the configuration all in one location and this information is value add to JIRA only users as well - what was the start, end, and release dates for a version. If JIRA folks wanted, they could use the same status mappings for their roadmap gadget. So, instead of showing just red and green, this gives them the ability to show red, yellow, green - thus, users of both products benefit.

When GreenHopper moved over to the new scrumb boards (and moved the old versions of boards into the "Classic" view section), the JIRA dashboard and wallboard and Confluence gadgets still only had functional compatibility with Classic boards. There's issues entered into the GreenHopper requesting that the old gadgets work with the new boards:


That worked! Thanks for the help!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 29, 2018 in Jira

How to set up an incident workflow from the VP of Engineering at Sentry

Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...

1,083 views 0 8
Read article

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