We use a form of Kanban during our development process, but the stories we complete throughout a release cycle all have the same fix version of "Product Version xxxx".
Previously, we could make intermediary WIP releases throughout the cycle simply by clicking the 'Release' button on the kanban board - we'd specify what this intermediary release was, and the stories would have this intermediary version ADDED to the existing main product release version. This was great, it allowed us to:
With the new Release button, you only have the option to release a pre-defined version - it forces you to go through your stories BEFORE they are done and decide that they will be ' released' together. First off this seems to go a bit against the Kanban method, forcing you to plan a release rather than releasing on the fly when ready.
Secondly, in our specific cases, this forces us to re-open issues and bulk change them in order to append a version before we do our reviews and intermediary releases.
Does anyone have any similar issues with the new Release button? How did you get around it, or modified your workflow to better work with it?
You can bulk change when items are in the last column too, effectively making the workflow '1) add new version to the things you are about to release 2) then click Release → <your new version>' working pretty much the same as the previous link.
If you have only one task to release – it's simple, you can add new version even in the right-hand panel on the board. If you have multiple task, just highlight all of them (Click while holding Ctrl) and then Right Click → Bulk Change.
(tasks can be in multiple versions at the same time)
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG