You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Join now to unlock these features and more
We noticed an update yesterday by Atlassian that allows the open subtasks to show in the scrum board even though the parent is closed. This is causing the Backlog to be littered with these subtasks and confusing the users.
Any idea why this update was introduced?
I don't quickly have the details ready why this has been done, but you can exclude them by adjusting your JQL.
In relation to your request, I do some remarks (my opinion off course)
We do not allow issues with sub-task to be closed if it has open sub-tasks, as this raises questions in our sprint review and even PI review.
Why are the issues not closed, are they not done, then we have a guideline, that they have to be cancelled. This to make sure that we do convince our stakeholders on delivery
Yes I do know you can close parent issues without closing sub-taks, but in our instance we use automations and workflow conditions and validators to block this behaviour.
But as I said in my reply this is an opinion we have in our company, Atlassian is not preventing this by default.
But it has been possible to show sub-taks on a backlog, this could be done by adjusting the filter used on the backlog board.
Are you sure no one has updated your board filter?
Sub-tasks are also showing in the backlog of the if Enhance my board and backlog is off.
I made a new default company managed project, based on Kanban. I did the same with a Scrum project and there sub-tasks are not on the backlog or board.
So kanban it has been there, scrum not. So in my opinion it can't be the new enhanced board feature.