Show subtasks on Jira Agile Planning Boards

[dylee]

+ 1 for showing sub-task under Sprint planing screen

[Anders Brogestam]

@Benito Picarelli, is there an update on this issue?  Seems like it is affecting many, incl myself, so would hope that it is fixed, or at the top of your backlog.

I think it's standard to create sub-tasks of a Story, assign to different developers to complete their sub-task and want to see it all in the board. And this includes seeing the effort per person.

Regards,

Anders

[robertrivera]

+1 for to show sub tasks on the backlog/plan view... indented under main story would be nice.. 

[Jim Kleckner]

At least show that a story has sub-tasks in the summary view.  Is that already possible?

[Alex Kwiatkowski]

Yes Jim, I found a way this morning! Please see the other comment I just posted.

[Chris Chan]

+1 for this request.

[Kathy Adams]

+1 Please add sub-tasks to the Backlog view under their tasks.

[Michaela Gluchow]

We are running v7.4.0 and the Kanban Backlog provides the feature of showing the subtasks. But then, this version is not yet providing Epics for Kanban. So you can choose 

-> sub-tasks -> Kanban

-> Epics -> Scrum

But as far as I have read, they are on it to provide the Epics for Kanban. Don't know what the plan is for the Scrum Board. ;)

[Prem Chudzinski _extensi_]

Upgrade to 7.5 and you'll have epics on kanban

[Michaela Gluchow]

hi. Oh wow, that was fast. Haven't watched the feature development for 4 weeks and swoosh it's there. Thanks for the information!

[Prem Chudzinski _extensi_]

@Michaela Gluchow you're welcome

And if you want to filter the epic or version panels check this :)

[Michaela Gluchow]

Thanks for this. Using this already ;)

[Garret Wilson]

+1

Please do this. We all want it.

[Marc Gerstmair]

+1 for having an option to show sub-tasks in the agile planning board

[Sean Moreland]

Agree with this option.  Nice feature for visibility to the agile board.

[Chris D]

I am currently in the dilemma of choosing between rearranging my entire task hierarchy, or ditching the agile functionality. I'm trying to get my team to accept JIRA, but every time I run into one of these "Atlassian says no" issues, it becomes harder and harder.

[Steve Miller]

+1 This is causing us huge headaches.  Seems to be very basic functionality that most users would need.

[Joshua Baptiste]

+1 For this "feature"  - I can't believe this has remained un-resolved for this long

[Rick Wohlers]

This is unbelievable. They won't let me use this tool the way I want to use it? No wonder everyone hates jira.

[Luke Browell]

+1 for config option to show subtask estimates summed for stories on the scrum board when using time to estimate stories (regardless about how you feel about this).

[Will McCall]

I can see subtasks as cards on my boards. Am I missing something?

Board Settings > Swimlanes > Base Swimlanes on Stories!

[florent hiebel]

people wants to display the sub-tasks in the backlog, not in the sprint boards

[florent hiebel]

https://confluence.atlassian.com/jirakb/how-to-display-sub-task-below-the-parent-task-in-the-backlog-779158697.html

[Michaela Gluchow]

I've tried this, but the initial problem remains. There are no sub-tasks in the backlog. Not the order is wrong, but they simply are not shown. 

I just use a filter for the project, ordered by rank asc.

How did you get your sub-tasks into the Scrum backlog in first place?

[ashwini]

Is there any solution to this still ?

[Matthew Walker]

Though not available on scrum boards, it may be helpful to some to know that subtasks are available on kanban boards. In the below shot, you can see task LVWB-12, and its two subtasks, LVWB-13 and 15, underneath it.  Again, this isn't going to satisfy those needing subs in a scrum board, but for some projects it will help. 

Joining the chorus here, it's beyond me why Atlassian, with all the flexibility they do offer, won't allow subtasks to be posted to scrum boards.  This position forces users into painful (at best) and impossible (at worst) scenarios, requiring complete reconfiguration of all subs to tasks, tasks to stories, and stories to epics, and even epics into Projects (?).  This is actually a pretty serious flaw in their featureset.

 

[Niklas Bergh]

+1 for this;

We are use subtasks under a primary in order to group relatively small work packages (approximately 5 items for each group), the group is managed as a bundle, but individual subtasks are executed by different individuals and have significantly different lead times and state blockers.

Not being able to visualize these sub tasks in a scrum board is a notable issue.

[Vladislav]

I would love personally to see this at least as an optional setting. Default off, just option for people that want to see it can see it. 

[Joel Marshall]

I can't believe this is still an issue. It's been a painpoint since we started using JIRA over half a decade ago. Listen to your customers, Atlassian. Make it an optional feature. It's obviously in demand.

[B5A7]

+1 for this request.

[Andrew Hillson]

+1 We need to see sub-tasks on boards as well. Re-structuring our project hierarchy will be a major pain.

[rpgptbr]

I agree, this is really needed functionality.

I hope they add this in a near future!

[Lee Lance]

Subtasks are only ever children of a particular parent Task or Story right?

So when I go to the planning / backlog board, and click on, say, a Story... and look in the right-most panel, I can see subtasks. If subtasks are just details of a Task or a Story, then why do you need to see them on the planning board, if you're planning at the Task or Story level?

If you move a Task or Story into a Sprint, you'd want all those subtasks to follow.... You couldn't leave them behind, right? So it would seem to make no sense at all to see subtasks on the planning board / backlog outside of the Task or Story they're subtasks of.

I think having subtasks on the planning board itself would be problematic because it would allow you to drag a subtask to a sprint without it's context/parent/story/task.

If we are only partially through an item in a Sprint when the Sprint ends, we simply roll that item (Story or Task) into the next sprint. All of the ToDo/InProgress/Done statuses are preserved.

Screenshot_2016-09-28_08_48_16.png

SBY_board_-_Agile_Board_-_JIRA.png

[Aaron Sua]

See my above comment about teams of specialists rather than teams of generalists

[Michael Collins]

Hi @Chris S, a technique that has worked for us is to create a custom *Link* type in Jira between tasks (not sub-tasks) and stories. This custom link allows you to create a similar association that exists between the out-of-the-box sub-task/user story relationship but enables capturing story points within tasks. Here's how you set it up: 1. Log in as a user with the JIRA Administrators global permission. 2. Choose > System. Select Issue Features > Issue Linking to open the Issue Linking page. 3. In the 'Add New Link Type' form at the end of the page: Enter 'Dependent' in the Name text field. Enter 'depends on' in the Outward Link Description text field. Enter 'is dependent upon' in the Inward Link Description text field. Click the Add button. Once you have this link configured, you can link tasks as 'is dependent upon' the user story. How to set the relationship in Jira tickets: Task [depends on] Story Story [is dependent upon] Task Side note: this is also a great way to create a Kanban release ticket that spans one or multiple projects. See http://bit.ly/1SnGRl8 for full article on linking. Hope this helps! -Mike

[Aaron Sua]

I did something similar, creating a Child-Task issue type and associated custom links.
I also went so far as to create a separate workflow for Child-Task that has additional validations and post-functions to simulate the Sub-Task functionality.  In JIRA cloud however it is hard/impossible to simulate the "All sub-tasks are complete/incomplete" rule set. 

[Lene Solberg]

I just discovered the add-in for Automatic creating sub-tasks, and I was so happy.. but just for a short time.. seams like I have no need for it as long as I cannot see the sub-task in my agile Board. This is on the top of my wish-list :-)  Hope you find a way to implement the functionality, so the users of Your system can choose if they like to see the sub-task in agile Board or not..