How do I filter a Kanban board by stories and their linked issues?

rpatrick

For context: I have a Kanban board currently sorted into swimlanes by Epic. Epics represent clients, and stories represent projects for that client. I would like to add a JQL query or quick filter that will allow my team to filter down to a story and its related issues/tasks. My problem is that I can't find a way to do this dynamically; we create a lot of stories/projects and do not want to create an individual query for each one. I did not see a way to make an automation that does this. 

Any help or guidance is greatly appreciated! 

 

Edited to add: I have tried creating a separate board that categorizes swimlanes by Story but it doesn't separate anything. I also tried the GROUP BY feature with the same result (all issues are combined in the board and not actually separated). 

Trudy P Claspill

Hello @rpatrick 

Welcome to the Atlassian community.

Using the Group By/Swimlane feature set to Stories will give you each Story (standard issue type) as a swimlane with its Subtasks (children) shown as cards in the swimlane.

There is no feature that will let you create swimlanes per standard issue type (story) and show within the swimlane cards for the issues linked to the story.

Jira Cloud also does not have a native feature to allow you to dynamically filter down to individual standard issue type (story) issues.

You could use the Labels field to create a "tag" for each "client project". Apply that tag to each Epic, Story, and linked issues. Then you can filter the board dynamically by the Label value, since Jira automatically provides a dropdown multiple-selection filter for the Labels field. This assumes that all the linked issues are within the scope of your board's filter.

Alternately if you are open to an alternate organization of your issues, you might want to consider making a Jira Project for each client, then convert your Story issues to Epics within the appropriate Client Project, and then convert the linked issues for each converted Story/Epic into a child of the Epic. This assumes that the linked issues are linked to only one Story. If they are linked to multiple Stories this might not work, since a standard issue can be a Child of only one Epic at a time.