Subtasks no longer visible in board

[Tomasz Armata]

I have my sprint board filter set to

project = PLAN AND type in subTaskIssueTypes() ORDER BY Rank ASC

Last week i was able to see my subtasks in board. Today i cannot see them.

Only difference i know is that new sprint was started.
So I have tried to filter out (in /issues page) subtasks which should be visible by adding sprint condition

project = PLAN AND type in subTaskIssueTypes() AND sprint in openSprints() ORDER BY Rank ASC

 This filter gives me 34 subtask back.

I also check in board settings the Column management. And it shows me that there are some items in few columns.

I have option "Enhance my board and backlog" turned in. But i didnt change that option last week.

[Trudy Claspill · Accepted solution]

Hello @Tomasz Armata 

Welcome to the Atlassian community.

What is your Swimlanes setting for the board?

I find in this scenario the subtasks are visible only when the Swimlanes are set to Stories.

[Tomasz Armata]

I had queries swimlanes to separate priority and non-priority issues.

[Trudy Claspill]

In that case the subtasks will not be visible as separate cards.

It appears that for every Swimlane setting except Stories you need to include the parent issues of the subtasks in the board filter. Without that the subtasks will not display.

Did you change your Swimlanes setting compared to last week?

[Tomasz Armata]

No, i didnt change them. Seems like some jira update caused this behaviour.

[Trudy Claspill]

I have never noted how this behaved in the past.

Atlassian posts messages weekly about changes in functionality. You might want to look through them to see if there is a changes that seems applicable.

https://confluence.atlassian.com/cloud/blog/2023/09

[Tomasz Armata]

I looked through the last 3 posts and unfortunately found nothing suggesting a connection to the topic.

I appreciate your interest. Thanks :)

[Tomasz Armata]

O, look @Trudy Claspill! They reverted that change ;) Its working again! :)

[Trudy Claspill]

So they did. Hm, I wonder which change caused that.

[Tomasz Armata]

I'm happy but also not because I'm worried about what my company would say about switching to jira cloud from the current system if the setup was already in production and would stop working without any mention of such a change in the release notes. Will see.

Again, thanks a lot for Your help!