Automatic task structure (structure builders)
Contents:
|
|---|
Overview
The task structure or hierarchy within a box can be generated automatically by the app. You can set the rules to structure your tasks by activating respective structure builders.
The order of structure builders reflects the levels of the hierarchy; in other words, the first structure builder determines the highest level within the structure.
Security and access
Only a user with a (minimum) Box Admin security role can access and change the box configuration.
To change the task structure configuration, go to Box configuration > Tasks > Task structure.
Hierarchy in Jira
While the structure algorithm is very advanced, some hierarchies are impossible to generate automatically. This is due to Jira's limitations and because the app cannot duplicate tasks in the hierarchy. Read more about Conflicting structure builders .
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.
Types of structure builders
There are two types of structure builders:
built-in
link-based
When you activate one of the built-in structure builders, a task representing a Sprint, Component, Version, or 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 can also be used as structure builders.
Templates
The table presents the available configuration options.
Task structure option | Description | Screenshot |
|---|---|---|
Agile | Organizes tasks into a hierarchy of epics and sub-tasks, ideal for single-project Agile teams. |  |
Agile (multiple projects) | Adds the project level above epics and sub-tasks to support multiple Jira projects in one box. |  |
Release | Structures tasks by project, version, and sub-tasks, making it easy to track work across releases. |  |
Objective & Key Result | Builds the task hierarchy based on the relationships between the Objectives, Key Results, and the issues linked to them. |  |
Custom | Lets you tailor the task hierarchy to your needs by editing the Advanced configuration settings. | Expand the Advanced Configuration tab and enable the structure builders you want to include. The Custom mode will turn on automatically.  |
To activate custom configuration, change switchers in the Advanced Configuration panel.
On the right-hand side of the Advanced Configuration, you can see the Structure Preview of the tree structure. The warning about the conflict appears when the structure cannot be generated according to the user's preference.
For example, the hierarchy with Version and Jira Sprint structure builders cannot be shown, and as a result Version and Jira Sprint will be positioned at the same level.
Limitations
only built-in structure builders are visualized on the structure preview
link-based structure builders cannot be visualized on the structure preview
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.
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).
Example
Task structure configuration example:
When you reposition a task in a tree, a pop-up appears:
Synchronization of changes made in the app with Jira
When you manually reposition a task in the task structure, task fields are updated to match structure builders.
The sync mechanism mirrors the user's changes in the task structure in the app in Jira issues. In other words, if the user indents, outdents, or drags and drops tasks within the task structure, relevant changes in tasks' fields responsible for their position are done automatically in Jira. The fundamental prerequisite for the changes to be made is active Structure Builders.
Link-based structure builders cannot overlap with built-in structure builders.
Advanced Roadmap in Jira Cloud Premium
Advanced Roadmaps is available as part of Jira Software Premium and Jira Software Enterprise.
What is the hierarchy in Advanced Roadmaps?
Advanced Roadmaps (AR) uses the same issue hierarchy as Jira Software but can be customized and expanded to track larger goals above the epic level. For example, you can create an initiative hierarchy level to represent a program containing multiple projects or combined efforts spanning multiple teams. When positioned above the epic level, the initiative can be used as a container for epics.
Hierarchy in AR lets you create a WBS structure (similar to the task structure in the app). AR hierarchy can be activated in a Jira configuration via Manage Apps in a Hierarchy configuration option. Go to Jira Administration > Manage Apps > Advanced Roadmaps for Jira > Hierarchy configuration
Hierarchy is based on levels (with the highest at the top). The levels above Epic can be configured and additional levels of hierarchy can be added above Epic. You can change the names of these levels and structure the hierarchy to meet your needs.
Learn about how to configure hierarchy levels or how to expose these levels in Jira.
You can also use your AR hierarchy by adding the AR as a structure builder in the App.
Parent/Epic Link/Parent Link in the app
In Jira Cloud, 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 Parent field.
It is a single way of representing parent/child relationships to give you a simple, consistent experience for all levels in your Jira Software projects. epic-link and parent-link in company-managed projects are replaced with the parent concept already used in team-managed projects.
Structure builders in the app
With the Parent structure builder activated, the app shows a hierarchy based on a Parent link (also sub-tasks and Epic links). In this case, the Epic and Sub-Task builders are redundant.
With the Parent structure builder activated, the app does not allow the creation of indents that are incompatible with the Jira hierarchy.
Trello structure builders
When you connect external tools, you will see an additional section with Structure builders specific to that tool. In the case of Trello, these include Boards, Lists, Checklists, and Checklist Items:
Example
Let's generate a hierarchy resembling how data is presented on a Trello Board - tasks are organized into lists on the app’s Power-Up Public Roadmap:
Enable the 'Boards' and 'ListClear' structure builders.
As a result, tasks are organized in the same way as the Trello board.
Reset the structure (WBS)
Adjust the structure builders and click Save. The task structure is rebuilt accordingly.
Manual indents
Manual indents are visible in the app only (not in Jira):
all manual changes on the tree structure by indent/outdent
any adjustments on the Basic tasks
Manual indents do not create links in Jira or changes to fields (e.g., Version or Epic), as they are not connected to any structure builders.
Clear manual indents
Clear the changes that were manually made to the task structure.
The structure that was based on the structure builders is not affected.
Need support? Create a request with our support team.
Copyright © 2005 - 2025 Appfire | All rights reserved.