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
Next: Root
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
Bizarre glitch happened when configuring Swimlanes for my project.
The swimlanes were configured correctly, and I had the relevant issues that should appear in those swimlanes. So a swimlane should be showing up and displaying that issue in that swimlane. However it was not. Why?
I had other swimlanes configured using the same JQL formatting etc. that were working correctly. After pulling my hair out for a day, checking status names, editing the formatting, everything - still, the swimlane was not showing up.
A colleague came over and played around with the order of the swimlanes, pushing the swimlane that was not showing up to the top of the kanban board.
This made it appear. I had two other swimlanes with the same problem, but somehow going into board settings, moving the swimlanes to the top, made them appear on the board.
If anyone can explain why this fixed this bug I would very much appreciate it!
Hi Warren!
I see - so because Issue 1 was already configured to show up in swimlane A, even though I had configured a Swimlane B to show when Issue 1 is progressed into Status B, because it was already being displayed in Swimlane A it didnt generate Swimlane B.
But to me that seems odd, because isnt that the whole point of the swimlanes?
The important statement in my answer above is
an issue will only appear once on any board
The queries work from the top down and once it's displayed in a swimlane, you'll not see it in any other swimlane.
You should try to come up with mutually exclusive queries, so that you don't have this problem.