+1

Hello,

we need that too.

+1

+1

+1

+1 would be great to have this in Data Center as it just got implemented in Cloud re: JSWCLOUD-7992

Hi Atlassian, we need this :"(

Fix.

When?

+

If you've moved away from subtasks because of this issue, please vote for this ticket to improve the flow of working with regular tasks: JSWSERVER-21398

There have been multiple discussions in teams i am working with to have the sub-task view in scrum backlog view. Just a having some indication too will do if there are sub-tasks with an indication like "+" sign shown to simpyfy the solution which may be useful as visual indicator.

Hi, we are using planning approach with WBS based on Epic/ Story/ Task levels for top-down planning, then Tasks are going for buttom-up planning to development groups - it is done by Sub-Tasks. So our Sprint-Planning in Backlog is almost blocked and we in PMO ranning out of workarounds. 

I hope this use case would be implemented very soon! 

Thank you in advanse

Hi, we are implementing SAFe and we use sub-tasks in capabilities & features to bring them to DoR. As we work in ALL teams with scrum e.g. also in legal department, sub-tasks like “legal check” for DoR need to be assigned to a sprint within the legal team.

Hope this is reason enough to get this issue solved soon

+1

In our organization, sub-tasks are used for planning the personal availability of the developers team members. They should be shown in the backlog, just below / embedded to the issue types "Story", "New feature", "improvement" and (optional) "bug".

Thank you in advance .

+1

Subtasks are critical to Agile but overall, Jira needs to do a better job of displaying issues and it's hierarchy in backlog view.  

Note:  Unfortunately, Optimize does not render well in Data Center.  Very excited to try it and experimented with all the configuration and the icons just didn't line up in a way that was useable.  Keep working on it tho!

+1

Unfortunately the above Optimize app doesn't have a Cloud instance install........

As this has not been implemented for 7 years, we created a Jira app that does the job and also adds a lot of other features.

https://marketplace.atlassian.com/apps/1223194/optimize

Our stories have sub-tasks that need to be completed at least one sprint ahead of the main story implementation (e.g. change in an API response). And, this sub-task needs to be tracked in the scrum board. Please implement the feature.

We need this ASAP. We cannot use Jira for planning without this feature. What do we need to do to get this developed ?

Without this feature there is no point to use subtasks as you can not see them on the board. Otherwise the parent task is angind through 2 sprints in progress if it incorporates several child issues

This will be much helpful as sub-tasks are to invisible in the scrum board backlog view today. And it is very confusing that kanban boards it already works.

Would of course be even better with a filter button to hide/show subtasks in the backlog. Sometimes you want to see the sub-tasks and sometimes you want to hide them. 

+1

Why is this not a configuration option already?

+1 This is the singular feature missing from Jira that makes me go back to using TFS

+1

I agree  this would be wonderful and really useful to assist us in planning.

This will be very useful for our organization!

Thanks!

+1

Also waiting on this

Still waiting for this feature... its basic... thx

This Feature would be very helpful for our company!

We could use this functionality as well. 

Looking forward to seeing this rolled out soon.  Our team needs it as well. VSTS has it and I may actually need to switch over this.

This is needed basic functionality.  Without this, tickets seem to have gone missing.  Make it an option?

brus-per.hogstedt1739492966, tj5,
I commented on this issue 3rd November 2016 and added a current status message at the top of the page.
We've been making good progress on sub-tasks in the kanban backlog and will be looking to make improvements to the scrum backlog.
More generally there is a post on how the JIRA team uses jira.atlassian.com.

Kind regards,
Martin
JIRA Software

Is this the way Atlassian routinely handles requests by their customers?

Yes.

Evaluating JIRA for our team, I find it somewhat disturbing that a feature of this kind is not addressed. It was created 11/Mar/2013 and has been commented on by Atlassian 19/Jun/2014 where they stated that it is a valid request but that they could not resolve the problem during the coming 12 months. That is now 2,5 years ago?!I would like to know:

1. Is this the way Atlassian routinely handles requests by their customers?
2. Specifically, what is the roadmap for solving this problem/bug, when will a solution be available?

Thank you,

Brus-Per

It looks like this issue is getting some attention. While we all appreciate its complexity, i think we appreciate even more that it's being worked on.

Does the JIRA Software team have any sense of when these subtask enhancements will make their way in to SCRUM boards?

thanks,

adam

Hi Martin!

Atlassian Support directed me to this particular Suggestion.

Sorry I left such a disgruntled comment...I'm new to JIRA, and finding issues that I've created has just been really frustrating ("oh, we need to fix that thing!  Did someone already make an issue for that?" and then looking and looking and clicking through random tasks and then later discovering that duplicate subtasks had been made).

I'm glad to hear that what I thought was an easy fix is part of a larger project with other subtask improvements...looking forward to seeing them soon!

Katie

kallen1731685362 - did Atlassian Support direct you to this Suggestion or another one related to search?

We're working on the problem of sub-task visibility in the backlog, the first stage of which can be seen in the Kanban boards when the backlog is enabled JSW-6175. We're working through steps to make the sub-tasks useful for those that want them and not distracting or space-wasting for those that do not. There are many complex interactions involved in these changes and it's actually pretty hard, however, we're working on it.

Kind regards,
Martin
JIRA Software

Another fascinating angle on this issue: apparently, even if you know the exact issue key of your subtask, IT DOES NOT PRODUCE ANY RESULTS WHEN TYPING IT INTO THE SEARCHBAR.

Aside from the fact that you shouldn't have to memorize issue keys, and that subtasks should be much more visible for all the reasons stated above, EVEN IF you happen to know it (perhaps you named your branch after it) it will not come up in the search.

I submitted a very detailed help ticket about this, thinking it was a bug, but alas: Thanks for the explanation, we were able to understand exactly your need. However, the ability to see subtask search is not available at this moment. For that, there is an existent feature request...

So even though my brain works best with subtasks, that's it.  I can't really use them anymore.  Once you create one, it almost completely vanishes into the fog of JIRA.  

+1 for how hard can it be to fix these issues?

+1

This is critically important for our usage. We have to use subtasks under main tasks for bugs due to financial/billing reasons, and we cannot prioritize them in the agile board! This is ridiculous. I thought it was a bug for sure, only to find out it's a known issue. Please fix this! How hard could it be to include them?

Meh! Your users want this ... why won't you listen to us?

Sub-tasks are issues just as all the others are, they require planning, just as all the others do.

+1

+1 the same reason we stop using subtasks, which is so frustrating for our team, since they are so loving subtasks...

+1 to please reconsider.
This feature would really accentuate how it is that many users including myself would like to see the subtasks shown. It is possible to work around this but to plan the sub task using time (story points) and not have either rolled up in the Backlog and Board seems to make the SubTasks useless.
Please elaborate on why they are even here if this feature isn't feasible? The option of rolling everything up a level isn't really possible in this scenario (and others' scenarios).
Please reconsider this - thank you

+1 we have stopped using subtasks because of this short coming please consider implementing this feature

It would be very helpful, if not a must, to list associated subtasks underneath the parent story/issue when in the backlog.

Currently people get confused when they only see the parent and think that sub-tasks have not been created. It's only the details of the parent are displayed and scrolled to realize that the sub-tasks are there. When we are planning, we want to make sure that we have considered the tasks that would be needed to complete each issue.

Hi team,

Is there any update on the above? I do feel this is an important feature.

Thanks
arasu.b

One year passed again, how is this issue going? It's a very important function.
Is anyone working on it ?

Thanks !

I have to second @talr with this. Being able to see Sub-Tasks in plan mode is a necessary element for planning. Without it, it renders sub-tasks useless from a planning perspective. Time will have be tracked from the Issue rather than the sub-tasks, which can be assigned to multiple users.

When researching the possibility about this functionality outside of the JIRA forums, it is clear that a lot of users want this functionality and I kind of feel like we are being dismissed by having our support inquiries directed to a "Suggestion" that is roughly two years old. What is the status of this overall? After all the last comment said that you could not realistically work on this over the course of the next 12 months and it is now one year later.

Thanks!

Thanks for reporting this issue. We see this as a valid feature request, however realistically we will not be working on it in the next 12 months.

Thanks for your patience and we hope you appreciate our open approach to feature requests.

Regards,
JIRA Agile Team

This is a truly important request. I think marking it as "minor" is not doing it justice. Today, in agile planning mode, there is no way to know if a story has some sub-tasks defined without clicking on it and then scrolling down in the detailed view.
An indication of the number of sub-tasks on the story line will be highly useful.

Moreover, it will be great if the sub tasks could be displayed, for each story, as child-rows (indented under the story row) in the main pane of the planning board. They could be shown in read-only mode (e.g. greyed-out), preventing any change from these child rows, still allowing to see the whole picture in a single central location.
This can also reduce a lot of the criticism on JIRA's missing support of tree views and multiple-hierarchy.