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.
Hey,
I am using Multiple Filters Chart Gadget for the same purpose.
It lets you to group issues by number fields.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.