Brief summary of this article:
When creating a view with vertical and horizontal lanes you may see a number of empty rows or rows that you do not want to pay attention to right now. Displaying the correct information in the first few rows is important as data that didn't make it to the top can be missed.
This might be a bit confusing especially after having applied a filter for cards. For example, if you apply a filter to Tasks like
?Iteration is Current
the tasks from other iterations will be hidden but you will still see all user stories from the selected projects and teams.
In some cases Hide empty lanes button can quickly and efficiently make all empty rows and columns on your Board view invisible.
However it may happen that this button cannot address your use case. Should it happen, you're welcome to try to use Filters instead.
You can (and in many cases should) apply a filter to lanes as well. Generally speaking, a filter for lanes could be different from the one for cards, providing great flexibility in getting the view you need. In the example above you could apply the same filter to rows to see stories from the current iterations only. If you wish to filter out stories that have tasks in the current iteration (in other words, remove the empty rows), try something like
?Tasks.Where(Iteration is Current)
Also, you might want to hide the first empty row - “No User Story”. You can do it by adding “it is not None” to the filter. So, the resulting filter for rows would be
?Tasks.Where(Iteration is Current) and it is not None
Here are some helpful examples of the filters that could be applied to lanes in this board:
| Lane (Row / Column) | Card | Filter for lane | Result |
| User Story | Tasks, Bugs | ?Tasks.count > 0 | Stories only with Tasks |
| User Story | Tasks, Bugs | ?Tasks.where(AssignedUser.Contains(Me)) | Stories only with Tasks assigned to you |
| Feature | User Stories, Bugs | ?UserStories.Where(AssignedUser.Contains(Me)) or Bugs.Where(AssignedUser.Contains(Me)) | Features only with user stories or bugs assigned to you |
General principles
Syntax rules of filters above and below are described in the article on Advanced Filters. When you apply a filter to lanes, then cards are considered as inner Collections.
Helpful examples
Filters for Time List
Find a useful example in the article about Filters for Time list views and visual reports.
Filters by Projects and Teams
It is not possible to refer to currently selected projects and teams in filters so far. Instead, you have to manually list projects and / or teams one by one or use Me keyword to build smart reference in your advanced filters by projects and teams.
Filters for Relations
It is possible to apply filters to Inbound Relations and Outbound Relations lanes. More information: Filters by Relations
Filters for Roadmap views
On the Roadmap view, it is possible to hide rows only. Columns and filters for them are not supported. The Backlog column contains entities that are not planned and are have not been started. It is not possible to hide a Backlog column on Roadmap views.
Still have a question?
We're here to help! Just contact our friendly support team.
Find out more about our APIs, Automation Rules, Mashups and custom extensions.