I have stories showing in two releases on the planning board

I have created releases like this:
Release 1 (this has no master)
Sprint 1 - master is Release 1
Sprint 2 - master is Release 1
Release 2
Sprint 3 - master is Release 2
etc....

I have 17 user stories (an issue type I created in Jira) that have the version of Sprint 2. 3 of those stories are showing up in the Release 1 view AND the sprint 2 view on the planning board and I can't figure out why. Any ideas?

Hi M,

When a version is a Master of other Versions, you will see in it all the Issues associated with this version and all the Issues related to its Child versions.

Using your example:
Your Release 1 has Sprint 1 and Sprint 2 as children
So Your Issues of Sprint 1 and 2 are basically also in your Release 1.
You can notice that if you look at an Issue of your Sprint 1 closely from JIRA normal UI, you will see that it will be associated with the fix Versions: Release 1, Sprint 1

On the issue cards you will see the committed version, in your case Sprint 1.

It will help you manage and have a global view of your releases. You will also be able to see Release burndowns as well as Sprint Burndowns.

I hope I was clear enough, if not please feel free to say so.

Cheers,

This does make sense. What I can't figure out is why only 3 of the 17 stories that are in sprint 2 are associated to release 1. The other 14 don't show up there. The only thing I can think of is that I assigned some to that sprint by dragging the cards inv the planning view and then did the rest via a bulk transition in Jira to save time. (and selected Sprint 2 only in the version drop down list)
Do they only associate to both versions if I used the planning board to drag the card to the release instead of editing the story in Jira and assigning it to a release?

Yes M,

If you drag your stories into the version box, GreenHopper will automatically associate your Issue to the targeted version and its parents if any (Could be n level version hierarchy).

If you create your issues and omit to select the Release 1, you will end up with only 1 fix version (Sprint 2) and so won't see it in the Release 1.

We have a Story in GreenHopper to actually repair the inconsistencies like the one I described, but it is still sitting in the unscheduled box. I might try to force it up.

Cheers,

Thank you!