Stories with subtasks aren't appearing in their own swimlanes even when I have specified the setting

[Indu Subbaraj]

I have specified in my board settings that I want swimlanes to be determined by stories.

Since about the last week, any new stories I add to the board with subtasks appear in `Other Issues` instead of their own swimlane. Is there currently a bug in JIRA or is it possibly some other configuration issue? Would appreciate any help!

[Majken Longlade · Accepted solution]

The first thing I would check is if the filter for your board is excluding sub-tasks, either by type or maybe the workflow has changed and sub-tasks are going into an unmapped status?

If you'd like help, you can paste the JQL from your filter and we can start there.

[Indu Subbaraj]

Thanks for your answer!

I don't think that's the issue because there are two stories with subtasks that do appear in their own swimlanes (the only difference I can think of are these stories already had subtasks prior to me starting the sprint).

But here is the JQL filter for the board:

`project = PROD AND squad = "Personalization Infra" ORDER BY Rank ASC`

The subtasks are in `To Do` status which is mapped to the `To Do` column of the board so don't think it's that either 🤔

[Indu Subbaraj]

AH! That was it actually - my subtasks didn't have the squad set. Thank you for helping me figure it out! Not sure why it wasn't inherited from the parent story though...

[Majken Longlade]

It wouldn't be, unless you have some automation to update the sub-tasks based on the parents. This is probably my biggest gripe with the existing JQL, you can't say "get me the issues that match this query AND their children or their parents".

[SITTER Adrien]

@Majken Longladeif you have scriptrunner you can do something like this:

For exemple if you want issue from PROJECT-A of subtasks type "subtasks" and their parent:

(project = PROJECT-A AND issuetype=subtasks) OR issueFunction in parentsOf("project = PROJECT-A AND issuetype=subtasks")

[Majken Longlade]

Thanks, I do know about that, and it's good to mention it in case others need the solution. Still it bugs me that this isn't built in JQL.

Cloud does have parentEpic, but if you're not trying to make a board for an epic, it encourages misusing epics as buckets.