Jira structure builders

While the structure algorithm is very advanced, some hierarchies are impossible to generate automatically. This is due to the limitation of Jira and because the App can not duplicate task in the hierarchy. Read more about on the Conflicting structure builders page.

Custom vs templates

Different tools offer different ways to automate task structuring. Out of the box, Jira provides Task<->Sub-tasks hierarchy or Epic link-based hierarchy, but you can build a much more advanced hierarchy using the App.

Templates

Open

There are three templates available:

• Agile

• Agile (multiple projects)

• Release

Custom

When you modify the Advanced configuration, you automatically switch to custom settings. 

Open

Structure Preview

On the right-hand side of the Advanced configuration, you can see the preview of the tree structure.

Open

A warning appears on the right if the structure can't be generated because of conflicts.

Open

Constraints:

• Only built-in structure builders are visualized on the right.

• Link-based structure builders can't be visualized on the right.

  Open

  

Types of structure builders

There are two types of structure builders - built-in and link-based. When you activate one of the built-in structure builders, a task representing a Sprint, Component, Version, Project will be automatically added in the task types box in the automated rules of the Scope definition page. The link-based structure builders use a Jira link to define the parent/child relation. Soft links that are marked in the App (go to dependency configuration to check the link mapping) can be used as structure builders.

Open

See the example

For example, the WBS - DEMO Box has a project with three tasks in the Box scope with no hierarchy:

Open

Let's enable the 'Project' structure builder:

Open

As a result, a new task representing the project (WD - is the project key) was added to the list as a parent task:

Open

Now, let's create an Epic and the WD-1 task to it:

Open

The last step is to activate the 'Epic' structure builder:

Open

The T1 task is now nested under the Epic parent task:

Open

"Parent" structure builder  

'Jira Advanced roadmaps' structure builder has been replaced with the Parent structure builder.

Atlassian introduced a unification of fields responsible for some parent-child relations (Epic link, sub-task, Jira (Advanced) Roadmaps). Parent Link is now handled by the same field (Parent). 

Inverse links

Only link-based structure builders have an "inverse" option. When a link-based structure builder is active an additional checkbox appears on the right in the "inverse" column. When you put a checkmark in the box, links of a selected type will be used in inverse to build a structure. 

In the example below, the task structure is based on "Blocks" links.

For tasks 1, 2, 3:

• 1 blocks 2

• 2 blocks 3 

Open

Multiple link-based structure builders

When multiple link-based structure builders are active, you can select which link should be created (when you make changes in the task tree).

See the example

Task structure configuration example:

Open

Result - when you reposition a task in a tree, a pop-up appears:

Open

Open

Open

Open