How can i hide subtasks from backlog but display them in active sprint like before?

[Shreyash Kulkarni]

Project - Company managed
Board - Scrum

Hi.

I am not sure if its because of any recent changes but sub-tasks are being displayed in the backlog as collapsible against their respective stories.

I have created multiple boards in the project and each board has a different set of sprints. Earlier only story and defect issue type were displayed in the backlog but as sub-tasks are being displayed in the backlog this is messing up the sprints I have set up.

For example, a sprint A that should only be displayed in Board X [as per the board filter i have set up] is being displayed in Board Y.

I can go in more detail about the set up if needed but I need a way to backlog going back to how it was earlier i.e only Story being displayed and not its corresponding sub-tasks.

----
Board set-up explanation

I will try to explain the set up as briefly as possible-

So there are three teams - A, B & C with three respective boards in the project - X, Y & Z.

There is no overlap between the members of the teams but obviously they share stories, defects etc so I have applied filters for all the boards assignee wise and label wise.

So lets say for team A the filter is - only the members (assignee) of team A and only the stories with the label A.

Label wise filtering - only relevant stories are displayed in the backlog
Assignee wise filtering - only relevant sub-tasks are displayed in the active sprints

After the recent changes, sub-tasks being displayed in the backlog is causing a problem.

Let's say Board Y has a sprint Y1 which has a story with label Y but that story has a sub-task which is assigned to a member from Team C/Board Z and has a label Z. What this does is that it displays the sprint Y1 empty in Board Z [refer below image]

And I have confirmed this, a sprint X1 from Board X was being displayed in Board Z so i deleted the subtasks with the label Z from the stories present in sprint X1 in Board X and after this the sprint was not being displayed in Board Z.

[Trudy Claspill]

Yes, the display of subtasks in the backlog as a collapsible section is a recent change. Refer to this article:

https://community.atlassian.com/t5/Jira-Software-articles/Coming-soon-View-subtasks-directly-on-your-backlog/ba-p/2506271

You can temporarily hide the subtasks using a Quick Filter with the JQL

issuetype not in subTaskIssueTypes()

However, I would question whether the inclusion of subtasks in the backlog is the real reason that a sprint is newly displayed in a board.

If the subtasks were already within the scope of the board's filter, then the change to simply display them in the backlog should have had no impact on which sprints display.

Additionally a subtask can't be assigned to a sprint separate from its parent issue. So the display of subtasks again should not be changing the sprints that are displayed in the board.

The filter of the board dictates which issues will be displayed in the board. And any future or active sprint associated with that those issues will also be displayed in the board. Is it possible that there has been some other change either to the filter for the board, or to the actual data used in the fields included in the filter? What exactly is the filter of Board Y (vs. Board X) and how do you expect that to restrict which sprints are displayed in a board.?

[Shreyash Kulkarni]

Hi @Trudy Claspill

Thanks for the response.

>However, I would question whether the inclusion of sub-tasks in the backlog is the real reason that a sprint is newly displayed in a board.

It is the reason, the sprints have been displaying in this way since the recent change.

I will try to explain the set up as briefly as possible-

So there are three teams - A, B & C with three respective boards in the project - X, Y & Z.

There is no overlap between the members of the teams but obviously they share stories, defects etc so I have applied filters for all the boards assignee wise and label wise.

So lets say for team A the filter is - only the members (assignee) of team A and only the stories with the label A.

Label wise filtering - only relevant stories are displayed in the backlog
Assignee wise filtering - only relevant sub-tasks are displayed in the active sprints

After the recent changes, sub-tasks being displayed in the backlog is causing a problem.

Let's say Board Y has a sprint Y1 which has a story with label Y but that story has a sub-task which is assigned to a member from Team C/Board Z and has a label Z. What this does is that it displays the sprint Y1 empty in Board Z [refer below image]

And I have confirmed this, a sprint X1 from Board X was being displayed in Board Z so i deleted the subtasks with the label Z from the stories present in sprint X1 in Board X and after this the sprint was not being displayed in Board Z.

I realize that I have not explained it as clearly as possible and it may seem convoluted but I hope you get the basic idea.

The quick filter fix does not work because although it won't show the subtasks it will still display the empty sprints.

That is why i didn't elaborate on the set up in my original post because if I could revert back to how the backlog used to be before the recent change it would solve my problem.

[Trudy Claspill]

I don't believe this is a configurable change that can be reverted by the customer (you).

I recommend that you raise this issue with Atlassian Support directly. This could be either an intended consequence of the change or a bug that needs to be addressed.

https://support.atlassian.com/contact/#/

It would be great if you can report back here what you learn from them, in case other community members run across this issue.