I'm a little confused on how to add a subtask to an issue in a Next-Gen project. Subtasks are enabled, and I do have the option to add a subtask to an issue in a classic project, but cannot figure it out in a Next-Gen project. Are they not available in Next-Gen/is there some other configuration that needs to be done to enable them?
@Daniel Günther You have to click on the Group by sub task to see them on the board.
Review on the board section:
Guys, only our admins can Sort the board "by" (including by subtasks"). So we end up with none of the team member being able to see their work on the board within the subtasks :( Cannot see how this can be set up.
I'm so disappointed to only be able to see subtasks when the board is grouped by subtask. What if we had 15 tickets on the board with subtasks being worked on over a couple months? The board would be so long and confusing. The subtasks look like regular tickets, and I want them to at least be optionally able to act like them. The way we would use subtasks on my team is I (as PO) would make a user story, and the team would breakdown the ticket into dev tasks, which would be subtasks. As PO, I want to see the progress of the subtasks on the ticket to completing the user story. Therefore, the subtasks need to be on the board and in the backlog like regular tickets.
As an aside, it'd be useful if the user could make issue checklist items into subtasks. Now, when you select to convert it to an issue it doesn't offer subtask as an issue type. I'd want it to be able to become a subtask of the ticket it was created from.
Additional concern / Issue.
When filtering the board by Epic, list by subtasks only display stories of the EPIC that DO NOT have subtasks. !!
in addition, it is not possible to assign EPIC to subtask as in NExt Gen Project only parent linkage seems available.
Please solve ability to display subtasks in board for any member, and filtering by EPIC...
I apologise for the frustration this is causing. We know subtasks is an important part of your workflow and we are working hard to deliver on the experience as soon as possible.
We're working through the last critical pieces of the features, making sure it all works in a performant way. We should start releasing subtasks to next-gen projects at some point next week if everything goes well. I will update this thread when we do.
For those of you that would like to be part of the first cohort of instances that we enable subtasks on; can you send an email to firstname.lastname@example.org with your hostname (e.g. xx.atlassian.net) in the body and with "Next-gen Subtasks" as the subject? I will subsequently reply to your email at the point we turn on the feature flag for your instance.
Thanks a lot for your patience!
All - Here is how I got this working.
If you scroll above, you will see that I had sent an email 3 business days ago but no response.
I was having some other issue with JIRA here, so I had opened a ticket with them. While I was waiting for them to help me with that, I sent thme link to this page & told them I had sent an email 3 business days back & was wondering if they can help. The support person replied to my ticket within an hour saying he enabled sub-tasks. Maybe you guys can open a separate ticket to get their attention. Hope this helps!!
My Bad - subtasks do appear on the board. Not sure why it didnt show up in 1st place. but it shows now. Maybe it took while to reflect. this is the latest update to what was written below, so please ignore below (keeping the text below just for history) --
quick update -
The subtasks dont appear on the Sprint board to see the progress/status - to drag them from one column to other. All you see are stories & tasks!! (unless I am missing something in the time I got to explore. Just cant seem to like this next gen) - So enabling them isn't a great help!!
Hi Guilherme - Thanks for the reply.
Thinking more on what you said - if you dont want to see them on board then maybe you dont need it.
I generally like to see all subtask on the board under the parent & like to see the progress of each.
Again, everyone might be using it differently & I respect that.
Can you explain more, as I want to understand your perspective/reasons - maybe that might work for me too. Thanks for your help
Sure, I'd be happy to share with you. I suppose every team like to organize things differently and that is the charm of Scrum. :)
We are trying to have a good balance between detailed view and an organised backlog. So, in some cases, we'd like to use subtasks inside stories that are not showing on the backlog and sprints. That way I can organize different tasks for each one of the team while keeping all together in one story.
I totally see a scenario where these tasks could be also showing on the backlog, as you want. But, if an understand correctly (I am new to Jira), this is the current behaviour of the next-gen Jira. If you link an issue with another issue (and you can select the type of their relation) they will be connected, similar to the way subtasks works, but will also be showing on the backlog.
Hope it helps.
Subtasks are not available yet in next-gen projects. But they are on the roadmap. They will be available later. You can find the roadmap for next-gen projects here:
There are some answers from Jira. Estimate in first quarter -
Sub-tasks even mentioned in next gen project documentation:
It is very confusing and frustrating they are 'in place' but can't be used properly.
Alas, using next-gen project caused our team more pains than gains so far :(
The roadmap has been saying sub-tasks are "coming soon" since October last year. How soon is soon?
If it's going to be another six months before sub-tasks are implemented I will switch back to Classic now.
It just seems Atlassian has gone quiet on what's happening with Next-Gen.
This is cause for concern.
Since I wrote this answer Atlassian has provided a lot more information. We still don't have sub-tasks but we have assurances they are working very hard on getting them out ASAP. I suggest everyone follows this issue: https://jira.atlassian.com/browse/JSWCLOUD-17155?focusedCommentId=1923019&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-1923019
This has been "on the roadmap" for over 4 months now... I thought the whole point of using Jira Cloud was that you get more rapid feature updates?
Not being able to break down the cards into more specific working items is infuriating, since not everything is an Epic that needs to go into the roadmap.
We'd be happy with even simpel "checklist" capabilities in the markdown/description, but we don't even get that...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event