Thanks, guys! Any plans to make the sub-task show on the board like they were on classic projects, i.e. not in swimlanes, but below the actual story card and indented? (Or with a placeholder header above the subtask if in a different column as the story)?

Swimlanes cause stories to show as lanes instead of cards which means you can no longer drag them to reorder or move them through the workflow, so I don't like them for that reason. The old classic swimlane-less way of handling sub-tasks was perfect.

Thanks!
Frans

deyanirad the rollout for subtasks is now complete, so you should be able to see it in your instance. Let me know if this is not the case.

Cheers!

please add sub-tasks to our board https://hexinnovlab.atlassian.net

Just tried this and its brilliant - one step closer to being able to move to Next Gen.  It's good that you are already thinking about how to add to the subtasks.  Just need version control now... https://jira.atlassian.com/browse/JSWCLOUD-17260

If I could give Atlassian a big ol' handshake I would. Thanks so much for rolling this out, and I can confirm it works pretty good so far on my next gen projects. You guys rock, and I really appreciate the hard work. I'm sure there were tons of long nights and shattered vacations, so do make sure these engineers, product owners, community engagement folks, all of you guys, get a well deserved break and then some!!

Hi everyone,

thanks for your patience. I'm pleased to announce that Sub-tasks are now available for most customers. 

Please note that we have rolled out subtasks to almost all instances and we are in the process of completing the remainder of the rollout. If you are unable to add the subtask issue type, then don't worry it's coming very soon to your instance.

You can learn more about the feature by reading this blogpost: https://community.atlassian.com/t5/Next-gen-articles/Introducing-subtasks-to-work-breakdown-in-next-gen/ba-p/1105389.

We hope you'll enjoy the feature!

Cheers,

Thanks for the update, Dylan. I had created a custom type sub-task - I presume that won't impact the roll out? I understand I will probably need to delete the custom issue type and but was wondering it would conflict in any way. Should I delete this custom issue type?

Hi mayurj / andrew.peacock,

Sub-tasks are currently being progressively rolled out - we're at 50% and should be at 100% very soon, we're just ironing out a few kinks with some edge cases. You can check to see if they have been enabled already by navigating to "Project Settings -> Issue Types > Add Issue Type". If the sub-task issue type is there then you're good to go.

If not, and you'd like to have sub-tasks enabled in your next-gen projects, please let our support engineers know. You can raise a request with them here. Otherwise, your sites will be enrolled soon.

Cheers,
Dylan @ Atlassian Support

Sub tasks seems exactly what we need. Is there anyway to enable these for our instance?

Is this available in early release for cloud?