Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,363,927
Community Members
 
Community Events
168
Community Groups

How to show subtasks in Agile Board backlog

Hi JIRA community,
I am trying to set some TASKS as SUBTASKS for created stories. In my JIRA-Test env, SUBTASKS seem to indent (makes it easier to read), and more importantly are visible on the backlog. However in my JIRA-Prod env, SUBTASKS are embedded within stories, and are not viewable from the backlog. Do you know how we can change this? 

JIRA TEST
jiraimage1.jpg

JIRA PROD
jiraimage2.jpgjiraimage3.jpg
Thanks,
Layo

1 answer

Hello! smile Read Using Plan Mode

An issue will only be visible in Plan mode if:

  • the issue is not a Sub-Task;
  • the issue's status maps to one of the board's columns (but not the 'Done' column);and
  • there is at least a status being mapped to the right most column. Eg. If you have the columns To Do, In Progress, and Done, ensure that you have a status mapped to In Progress at least. If you map all the statuses to the first column (To Do), you will not be able to see any issues in the Backlog.

 

To add to this, there is a good reason - sub-tasks are of little or no use in planning.  You can't rank them outside their parent issue (because it's logically nonsense), so there's no point in putting them in there.  You can't actually do anything with them even if they were in planning.

It is more convenient to rearrange the order of subtasks in the backlog as well.

Why does this work nowadays in Jira Server 7.12 kanban backlogs, but not in scrum backlogs? What's the reasoning behind this?

Just for people stumbling over this question in the future:

According to Atlassian official Jira Software certification prep course, the reasoning is that Scrum Product Owners should not care about sub-tasks.

Like M B likes this

Oh, for Pete's sake.  It's useful for Atlassian to facilitate doing scrum and agile "the right way".  It's not useful for them to prevent us all from doing it the way we need to if we don't have 100% buy-in to agile roles and responsiblities at our companies.

Like Luisa_Randon likes this

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events