Is there any way to sort sub-tasks in next-gen?

[Ryan Brideau]

Some of our tasks have a large number of sub-tasks, but there doesn't seem to be any way to sort them in next-gen. This makes reordering tasks into the order they should be done impossible. Am I overlooking a feature that would allow this?

[Dario B · Accepted solution]

Hi @Ryan Brideau ,

Welcome to the Atlassian Community. 

In order to set the right expectations, let's start by saying that Next-Gen project are intended to be simplified projects that do not have all the customizations/configurations available and that are intended to be used by teams that have simple requirements and that want to start working immediately, without having to spend time configuring too many things.

Also, Next-Gen projects are still under heavy development and don't have to be considered complete yet.

Once this has been said, as mentioned in the article: Introducing subtasks for breaking down work in next-gen projects the ability for subtasks to be ranked within their parent issue is something that is going to be added in the close future.

What’s coming next for subtasks?

We will be monitoring usage and feedback to help us understand the value you are getting from subtasks, and this will help inform the prioritisation of incremental improvements. For example, we already have on our radar to make the following improvements…

• Making swimlanes a user configuration rather than being an admin configuration

• Providing more visibility of subtask estimation at the parent issue, on the backlog, and in reporting

• Allowing for subtasks to be ranked within its parent issue

• Adding additional information in the swimlane headers when grouping by subtasks are enabled

• Making it possible to convert a subtask to another issue, for example a story or task

What’s coming in the future for work breakdown in next-gen?

As well as some incremental improvements for subtasks, we have a number of more bigger chunks of work to come for work breakdown. These include (not in priority order)…

• Improvements to how work is assigned to epics

• Introduction of “Actions”

• Workflow configuration (and rules) per issue type

• More reports and more flexibility for reporting

• Estimation roll-up across multiple levels of work hierarchy

I hope this explains.

Cheers,
Dario