Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

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

Mark McGarry
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 30, 2018

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 B)
    • 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? 

 

Thanks,

Mark

 

 

1 answer

1 accepted

4 votes
Answer accepted
Marc Jason Mutuc
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 30, 2018

Update your filter and include Component is Empty. 

Mark McGarry
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 30, 2018

Cheers Marc, seems to have done the trick and relatively simple too - bit of a face-palm moment. 

Board Filter Query below in case anyone else needs it.


project = Project AND (issuetype in (Story, Task, Sub-task) AND component = TeamA OR issuetype = Epic AND component is EMPTY) ORDER BY Rank ASC

Marc Jason Mutuc
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 30, 2018

Nice! Happy to help! :) Kindly click on the "Check" icon beside the answers to accept it as a solution. 

Amin Sharifkhani
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 25, 2019

thank you for the answer, helped me out greatly

Suggest an answer

Log in or Sign up to answer