Greenhopper6 scrumboard: sprint - version relation (best practice)

Hi Guys,

When we were using "Greenhopper classic view" we used to group all the issue of an iteration in a version.

With the new GH board view this is not easy to do so a question came out: "Is binding a sprint to a version a best practice?".

If no, how can i keep track of the "released artifact" in jira?

Thanks and regards!


1 answer

1 accepted

Hi Carlo,

We removed the strict link between versions and sprints because it does not make sense for many users (i.e. the items worked on in a sprint might not have any direct correlation to a version that will eventually be released).

You can still keep the items linked if you wish though. When you start the sprint go to the sprint report, then click the "View in Issue Navigator" link to see all of the issues in the issue navigator, then use Bulk Change to assign the issues to the version that makes sense. You can manage the versions in your project from the Project Administration page. JIRA includes some basic reporting around versions.


Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Thursday in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

752 views 5 17
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
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