Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

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,467,448
Community Members
 
Community Events
177
Community Groups

How to see sub-task collapsable in backlog?

Edited

I want to see my sub-task like bottom example, in my backlog of scrum, but a don't find the option to add this feature.

Screen Shot 2022-02-16 at 17.44.03.png

2 answers

Hi @Eduardo Carrada

welcome to the community!

Is it important for you to see your epic/sub-task structure specifically in the *backlog* view, or would you be open to other kinds of "issues lists"? Or in other words, what issue actions would you like to perform on this epic/sub-task structure?

Best,

Hannes

Because is more easy the management of the subtask inside the collapsable option than inside the story details.

On the story details list you only can add a description if you open the subtask, but in the collapsable option you can add description and more details over the details view of the subtask.

Gotcha @Eduardo Carrada - now this may not be exactly what you're looking for, but if you're open to solutions from the Atlassian Marketplace, you may like JXL for Jira. It's a full-fledged table/spreadsheet view for your issues that allows viewing and inline-editing all your issue fields - plus it supports issue hierarchies.

Here's how e.g. the standard epic/story/sub-task hierarchy looks in action:

hierarchy.gif

It's worth noting that there are a couple of backlog features that are yet to come in JXL, such as ranking via drag and drop. But depending on your use case, it believe it could save you quite a few clicks. More info at https://jxl.app. (Disclaimer: I work on JXL :))

Hope this helps,

Hannes

Hi all !

As I understand the need of Eduardo : "I want to see subtasks in the backlog view of my scrum board".

I verify this way to show subtasks :

  1. Install Jira from scratch
  2. Create a new scrum project with sample data

You'll see subtasks under stories on scrum backlog.

Then I tried to find difference between this fresh new board and others on my production instance with no success.

There is surely an option elsewhere but where ? 

(Subtasks are visible on kanban backlog boards natively as Eduardo said)

Regards.

Nope, you won't.  Scrum board backlogs don't show sub-tasks.  You don't need to see them in a Scrum backlog.  I suspect you've not created a Scrum project, or at least board.

Kanban boards show sub-tasks because Kanban simply doesn't have a concept of sub-task.  Every issue is an item that needs doing.

0 votes

Welcome to the Atlassian Community!

Sub-tasks are not sprint items, they are just a fragment of their parent story.  They have no relevance in the backlog, the backlog is for managing the stories and sprints.

Thanks for your response

Maybe this is the reason because I can see this option in a kanban board but not in a scrum board, but I think this should be a nice improvement because I more easy the management of the subtask from the collapsable option than open the subtask directly in the details view.

There's no value in having sub-tasks in the backlog display in Scrum, you can't actually do anything with them, and they're not something you plan for (which is what the backlog is - a planning tool).

They are useful in Kanban backlogs because every card is a Kanban item.

Even if you can't directly assign the subtasks to a sprint from the backlog, it'd still be helpful to easily see what subtasks remain to be done in a story on the backlog page. And you kind of can do things with subtasks -- currently, once their parent story is in a sprint, you can change the status/assignment of subtasks independently on the sprint board. Since our team's stories span days to ~2 weeks, we use subtasks for more granular planning and work assignment.

You can't put sub-tasks in a sprint, so that's a non-starter.

You can add the "sub task" field to the issue display in the backlog to get a display of sub-tasks within each issue in the backlog, but it's not a lot of use there.

Suggest an answer

Log in or Sign up to answer