How to select stories for releasing (through release button?)

Charly Granitto January 14, 2013

We've configured a rapid board with 2 projects... each project corresponds with a deployable unit, so when we make a release, we need to choose the stories corresponding with the component we want to release, then specify the version number, and so on.

The problem appears when we use the release button on GreenHopper RapidBoard, because it takes ALL the stories on the last column and set a version number for them.

However, we need to do that task selecting which stories are part of a particular release. How we can accomplish that?

2 answers

1 accepted

2 votes
Answer accepted
cgauterio
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
January 21, 2013

Hi CharlyG,

I'm afraid that is not possible. Greenhopper works with the concept of Sprints. Basically, you create a sprint, add issues to it, work on them and when clicking on Release, you will release the Sprint and all the issues that are completed on it, so there is no way to select the issues you want to release when clicking on the Release button.

Hope this clarifies a bit :)

Cheers,

Clarissa.

Radu Dumitriu
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 21, 2013

Do releases separate; on two projects, do two rapid boards.

"[...] make a release, we need to choose the stories [...]" = seems that your work philosophy does not match what I know about SCRUM philosophy.

0 votes
Charly Granitto January 21, 2013

Hi Radu,

We're using Rapid Board on a Kanban team... so then we don't have sprints. As Clarissa said, GreenHopper works with that concept. We don't work in that way, our team have issues from 2 different components (2 independent deployable units). For that reason, in a given moment, we want to deploy one of the components, making a release, considering some of the stories of the rightest column of the board.

We could configure a board for each component, but we still have one single team maintaing both components. One of the features of Rapid Board allows to configure a board with several projects, but we can't to release each project separately.

Regards,

Charly

Suggest an answer

Log in or Sign up to answer