You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I hope this blesses a lot of people, because I figured how out to do a Release and Planning Board with the new Jira. Here is the problem, and here are the easy steps:
Problem: We have sprints that include items from several projects. We use the Sprint methodology, but we had to create a shell project to lump all of our projects together into a single sprint.
Planning for VERSIONS was a huge sticking point, since Jira wants us to keep 1 project = 1 version. Therefore, we had to create a separate project called 'Releases' to do this. And while it has a little tedium, it's totally worth it - watch:
5. Configure Your Board - For your new Kanban board, configure it to have the names of the releases you have internally at your organization. This will make it easy for any kind of visual release planning. We leave the first column for 'All Cards', and the last for 'Released', with 5 lanes in between:
6. In your Releases project, create VERSIONS as the system allows. (this is why you do NOT delete the Agile board that comes with the project itself).
7. Add a single transition SCREEN to the RELEASED status. This will ensure you can update the actual version when it's deployed. The screen only needs to include 'Fix Version', unless you want to include more:
And that's it. Now you can create a proper Release board that visualizes what issues are in what release, and see it in a horizontal way. Also, you can create other boards that are not restrictive on status and easily drag and drop. Yes, you do have to clone your issues from time to time, but it's easy to maintain, as releases don't usually happen every day - I offer that you only create clone cards for issues in the upcoming sprint or so.