We having fun setting up a cross-project Kanban board & configuring swimlanes, one thing we're running into is that it displays really slowly, this seems to be due to there being 2500 issues in the 'everything else' lane - you can't seem to exclude this lane from the display - any ideas?
The swimlane will not appear unless there is something to show in it. So if you do not want it to appear you have two options:
Shaun - please can you let me know of a method of searching for items which only appear in the "Everything Else" area?
As the only way to "unpopulate" it is to perform an action on items which appear in it - it makes sense to provide an option for people to be able to search for items specifically in that area.
If it doesn't exist as a searchable option - I believe it would be a very useful addition for future updates of JIRA.
Performing bulk actions on issues in the "Everything Else" area, knowing that other swimlanes would be unaffected, would be hugely beneficial IMO.
This is a six year old post, and Software has been significantly changed since then.
However, the swimlane principles are very similar. If you want to remove the "everything else" lane, change your board query so that items that would fall into it are no longer selected by the board.
How you exclude them depends entirely on your swimlane set up. What are you currently using for swimlanes?
The swimlanes are based on Queries. Each swimlane is defined by fixVersion = SWILANE.
Not all issues were given a fixVersion - so some are blank. They would be relatively easy to filter out. It is the other items (c. 500) that are not so easy. That's why I would find searching specifically for issues held in the "Everything Else" area useful. Please let me know if you need any more info. I appreciate your assistance.
Ok, your queries are all going to be fixversion based, so, let's say you've got a simple scheme, where the first swimlane is "fixVersion = v1", second is "fixVersion = v2" and so-on through to "fixVersion = v5"
Alter the board query to say "And fixVersion in (v1, v2, v3, v4, v5)"
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
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