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 can see there are different columns in the next-gen project for swimlanes. I want to add new swimlane in the project but don't want an extra column for it on the board. Can someone tell me how to add extra swimlane but not a column on the board?
Atlassian has ruined what otherwise would be a great new version by taking away a really valuable level of functionality. When we have cross team initiatives, I wanted swimlanes to represent which team is currently responsible. Avoiding WIP and making this more self serve and obvious, where in the flow it is would be useful
You have access to only 2 pre-configured swimlanes (upper right of the board):
However you can still create a board with a filter on your Next gen project.
The workaround would be to create an empty project to hold this board.
In the top left corner, "Group by..." gives you the ability to divide the kanban view in swimlane like rows, according to Assignee, Epic, Subtask.
I used swimlanes for different production layers, independent on the Epic or Subtask. These layers in my case were across all Sprints and not a parent task or an epic. But then I was not using Epics to much.
Once forced to use Epics more often due to next-gen I ended up making use of the Roadmap feature as well. Previously I was using a 3rd party for Gantt charting.
I guess Atlassian is forcing us here in an updated management workflow, rather than a workaround. Though annoying, somehow the benefits emerge slowly.
Swimlanes, even basic ones based on a field, would really help arrange complicated projects with multiple validation steps - by being able to stack parallel or alternative flows. Simplifying process is a great thing to advocate, but life isn't always that simple.
e.g. 'Make a cup of tea' - you may want to capture, but not provide an explicit column, for each of 'add milk' 'add sugar' 'add sweetener' 'add lemon' 'add brown sugar' - It would be much better to have just two columns called 'sweeten' and 'milk or cream?' with the specific routes swimlaned out.