Subtasks in Next-Gen project?

[Mohammed AbuJubara]

Dears,

is there away ti switch back to my old jira from next Gen???

[Daniel Serodio]

https://confluence.atlassian.com/jirasoftwarecloud/migrate-between-next-gen-and-classic-projects-957974933.html

[Max]

Hi Atlassian team,

The sub task and next-gen project are brilliant features which we've been using everyday for our project management. However, It'd be the best if you can implement Create New Sub-task Type feature for next-gen project. Currently, our backlog is messy and expanded unnecessarily due to BUG created as a Issue type instead of sub-task type. It's really inconvenient for us to manage project. I hope we could have the feature soon.

Thanks, 
Max

[Miguel Fenoglio]

When will subtasks show in the Board?? Just like they used to do on "prev-gen". I have my team wiggling their thumbs until the parent ticket is assigned to them because they simply can't see what's on their plate for the current sprint... 

[Jeremy Crawford]

I'm trying to understand how Jira can come out with next-gen without sub-tasks!??  

[Vinícius Cassol]

Next-Gen projects are pretty easier and friendly to use, but we really need subtasks!!!

[Jaepil Kim]

+1  for subtask

[Vinícius Cassol]

Any update?

[Surajit Kundu]

+1 for Subtask

[Julien Femia]

Hi everyone,

I wanted to give a little update about how the subtasks rollout is going.

We have released the feature to all customers that have reached out to Eoin or myself directly this week. We are monitoring this subset of customers, and the good news is that everything seems to be going well. We will regroup on Monday (May 6th) and probably open up the feature to more people.

As I said previously, send me an email (jfemia[at]atlassian.com) with your hostname (xx.atlassian.net) in the body and "Next-gen subtasks" in the title if you really want to be part of the early cohorts using subtasks :)

Once again, thanks a lot for your patience!

[Dwight Pfundstein]

Just sent !

[Thomas Holenstein]

Thank you Atlassion for the sub task feature.

Is there a solution for sub sub tasks?

[Charles]

We use sub-tasks to track time as our team measures both the sprint time scope parameters.
Therefore I see little that is useful in next-gen without subtasks.

That said, I'm aware that many teams use Jira in an unstructured free and frankly terribly ineffective way. So I can see how most would get by without sub-tasks as it would not change the mess they are in.

However, sub-tasks,  data/performance measurement, and display of these are core differentiation for Jira. So without sub tasks I might as well switch to Asana...

I hope that 'next-gen' will not become 'current' until it is on par with the existing Jira.

[Craig]

I gave up waiting and converted my next-gen project to classic. It was a PITA (has to be done manually) but at least now I have something usable.

[Thomas Holenstein]

yes. Me too, today. Unbelievable, that I have invested a lot of time to build up in this project. Jira, please wake up!!!

[josh]

Yeah I just converted my one "next-gen" project back. Only thing next-gen gave me that I liked was the Roadmap. Otherwise its feature set was too anemic to keep using.

[Jack Hunter _HeroCoders_]

If someone does not need the full set of rich attributes that come with Jira sub-tasks like Description, Comments, Labels, etc. then the list of lightweight ToDo items (with checkboxes) attached to the issue might be a decent workaround. 

Issue Checklist Pro, the paid app, or its free sibling Issue Checklist Free, provided by my team and presented in the screenshot below adds the checklist panel to the issue page and works in the next-gen projects.

It gives a simple user mention functionality (no notifications yet), due dates, completion progress bar, automation support, default checklist concept, templates and more. 

The full set of features it provides is described in the documentation.

I hope it helps. However, I wait for next-get subtasks and other improvements impatiently too :)

Cheers,
Jack

[Craig Patchett]

It should be noted that this is not a free solution.

[Jack Hunter _HeroCoders_]

Thank @Craig Patchett. I have updated the answer to reflect that. 

[Jack Hunter _HeroCoders_]

Actually, we also offer a free solution now: https://marketplace.atlassian.com/apps/1220209/issue-checklist-free?hosting=cloud&tab=overview

[Zak]

Do you have a release date for subtasks ?

I do not see it in your roadmap. 

[Karine Jannetta]

They already do.. you have to select "GROUP BY: Subtask" on the "GROUP BY" dropdown at the top right corner of your Board.. 

[Miguel Fenoglio]

Thanks, but destroying my board with that subtasks grouping is not an option for me. I don't want my board grouped by subtasks, I just want subtasks to show (as they did).

[Karine Jannetta]

gotcha.. it didn't seem to destroy our board when we used it (for a small test project). sorry it's not working for your existing project. TBH we haven't transferred any complex projects to Next-Gen at this time for the current lack of feature parity... so I totally get it!!

[SR]

does anyone know if this has been fixed now in Next Gen?  Can you see subtasks on the board?

[Miguel Fenoglio]

You can only see subtasks on the board if you group by subtask. You cannot see them otherwise (which also means you cannot group by anything else if you want to see subtasks).

[Chris]

This is a good point. I'm not sure what the solution is though. I don't think you want tasks and subtasks in the same list without being able to easily distinguish them. Perhaps it should always show the view you get when you "group by subtasks" and the main tasks are then grouped by whatever you choose.

[Miguel Fenoglio]

IMHO, it'd be as simple as adding a toggle to show/hide the subtasks in the same way they were shown in "old-gen". I understand some may find it very cumbersome if subtasks were always shown, that's why a toggle would be good. Having swimlanes for the main tasks has 3 problems:

1- It doesn't allow having swimlanes for something else, while being able to see subtasks.

2- Takes up much more space on the board than the "old-gen" subtasks display. It fragments the board.

3- Interaction with the parent task is more limited (ie. you are not able to see any additional details at first glance, you can't drag it to a different state, etc.)

It's just a matter of making available what was already there in "old-gen" with the enhancement of a toggle. My 2 cents.

[Jacoby Hickerson]

Agreed, this is the only thing missing before I would have my team use nextgen.  The ability to have a system default one way or the other and letting the user choose would be best.

[Guillaume Simon]

In the JIRA PLATFORM section of  https://confluence.atlassian.com/cloud/blog/2019/04/atlassian-cloud-changes-apr-22-to-apr-29-2019 I see :

Create and customize subtasks in your next-gen project

Need to get a bit more granular with how you track your work? Add a subtask issue type to your next-gen project and track the small tasks that help you break up and complete bigger pieces of work. Go to Project settings > Issue types and click + Add issue type to try it out.

Is it live ? I can not do this in my next-gen projects :-/

[Lukáš Brchl]

Read the comments above yours

[Guillaume Simon]

Thanks @Lukáš Brchl 

[John Testa]

+1

Our team is also waiting for this.

[Lukáš Brchl]

Sub-tasks for next-gen are now working. I suggest you reading this post https://community.atlassian.com/t5/Jira-questions/Subtasks-in-Next-Gen-project/qaq-p/921446#M340356

[simon]

why have you posted that sub tasks for next-gen jira are working? your link contains complaints about it not existing, i can't see a solution 

CLICK BAIT ALERT! :)

[Lukáš Brchl]

Have you tried the link? It refers to the statement of Atlassian employee. 

[Ian M]

Hi, I had a hunt around and found the subtasks as follows:

If you are on your project page and go to "Project Settings" and then in the left hand column select "issue types", then in the same column you can "add issue type" at which point you select to "add Subtask". THEN, if you go to a regular issue in your project you will see a new icon that looks like a small tree hierarchy - when you hover the mouse over the explanation the text "add a child issue" appears - that is the sub task feature for next-gen jira.

[Doris Han]

Hi, when i 'add issue type' I didn't see 'add subtask' yet. Do I need to 'create issue type'? 

[Ian M]

OK, if you do not see 'add subtask' if may mean I only see it because I asked to join the beta programme for seeing this feature and it is not yet released to all. My apologies. However, you can follow these instructions to have subtasks enabled earlier for your good self: 

"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 jfemia@atlassian.com 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."

[Doris Han]

Thank you Ian. I shall try this first! 

Appreciate! 

[Doris Han]

Please add subtask !!!!

[Thomas Holenstein]

Hey whats up with Jira new generation project sub tasks? I thought it takes only few weeks. If no, why you publish such kind of unfinished feature? Please update us about the subtasks. When is it finished?

[Deleted user]

Is there an updated ETA for sub-tasks on a next gen board? we're having difficulties without them.

[Dimitar Rupov]

Subtasks are a stopper for us to switch to NextGen also.

Would be really nice to get some kind of estimate.

Thanks

[Furqan Iqbal]

I gave up on Jira and moved to Clubhouse.io - created by developers fed up with the complexity of Jira 

[Packen Development]

I still can beleive they don't have subtasks in next gen projects. Even though its first in the list they have not implement it yet!!!!

[ashok vallabhbhai sudani]

I think before introducing such breaking change there should have been an excercise conducted by Atlassian to take opinion of customers either though poll/online forms.

You are encouraging customers to move to next gen project which you are marketing to be something brilliant but then again adding features which are removed without end user consent.

[Michael Yokota]

++1