For example, I have two swimlanes driven by JQL:
If userB is assigned a ticket where userA is the implementer, then which swimlane is the ticket supposed to be in? And why?
I’m confused by the point of the question at this stage. Given an issue can appear only once on a board if the filters associated with swimlanes could result in more than one possible location then the application needs to resolve the conflict. It seems to be a natural choice to work top down given.
the only way to control it is thru your filters and the order of swimlanes.
Why it happens is simple - if you put an issue on a board twice, it's misrepresenting the information. If you have 5 issues, but 7 "cards" on a board, that's wrong, and confusing to your users. You should only have one card for each issue.
The logic for it landing in the first swimlane is human too - the first swimlane is at the top of the screen, and hence the first a human reads. The board renders a card on the first time it sees it and drops duplicates thereafter.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs