nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Project with multiple boards, filtered by component, swimlanes grouped by epic = no stories on board

Mark McGarry

Hi,

I need some advice around swimlane grouping for a relatively complex project setup.

Our Project has multiple distributed teams working across one backlog.

We have created separate Boards in the project for each team by using the Component field as the filter, and each story that is created is tagged with the appropriate Component value for the team that will work on it:

Project with Epics X, Y, Z

Board A (filtered by Component = Team A)
- Story 1 (Epic X)
- Story 2 (Epic Y)
- Story 3 (Epic Z)
Board B (filtered by Component = Team
- Story 3 (Epic X)
- Story 4 (Epic Y)
Board C (filtered by Component = Team C)
- Story 5 (Epic Z)
- Story 6 (Epic Z)

In the above example, grouping the swimlanes by story is no problem - everything shows on each board as expected, however we want to group the swimlanes on each board/sprint by Epic, but it seems that unless the Epic is also tagged with the appropriate team-restrictive Component value, the stories will not appear on the board. i.e. rather than being able to be spread out across all teams, the epics become relative to a team/horizontal slice of the overall functionality, which is not what we are trying to achieve.

Is there a way to have a board filtered by component, with the swimlanes grouped by epic, where an epic does not also need to be tied to the component in order to show the stories related to that epic in a board/sprint?