Introduction
The task structure or hierarchy within a box can be generated automatically by BigPicture. You can set suitable rules to structure your tasks by activating respective structure builders.
The order of structure builders reflects the levels of the hierarchy, or 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.
Jira Structure builders
An Index corruption might result in a loss of structure on Jira server, if a user opens one of the Boxes and the synchronization is triggered.
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 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.
Templates
There are three templates available:
Agile
Agile (multiple projects)
Release
Custom
When you modify the Advanced configuration, you automatically switch to custom settings.
Structure Preview
On the right-hand side of the Advanced configuration, you can see the preview of the tree structure.
A warning appears on the right if the structure can't be generated because of conflicts.
Constraints:
Only built-in structure builders are visualized on the right.
Link-based structure builders can't be visualized on the right.
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.
Parent's movement in the structure does not replace custom Links by Epic Link. The Epic Link for the task is not changed.
For example, the WBS - DEMO Box has a project with three tasks in the Box scope with no hierarchy:
Let's enable the 'Project' structure builder:
As a result, a new task representing the project (WD - is the project key) was added to the list as a parent task:
Now, let's create an Epic and the WD-1 task to it:
The last step is to activate the 'Epic' structure builder:
The T1 task is now nested under the Epic parent task:
"Parent" structure builder - Jira Cloud only
For Jira Cloud, '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
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).
Task structure configuration example:
Result - when you reposition a task in a tree, a pop-up appears:
Move tasks manually
When manually repositioning a task in the task structure, task fields are updated to match structure builders. The sync mechanism is responsible for mirroring the changes done by the user in the task structure in BigPicture in Jira issues. In other words, if the user indents, outdents or drags & drops tasks within the task structure, relevant changes in tasks' fields responsible for their position are done automatically. The fundamental prerequisite for the changes to be made is active Structure Builders.
Built-in
Built-in structure builders' values are applied to all nested tasks (regardless of the indentation level). In the example below, the 'epic link' has been used as a structure builder.
Link-based
Link-based structure builders are applied only one level down (to a direct child of a task).
Multiple link-based structure builders can apply at the same time. Link-based structure builders cannot overlap with built-in structure builders.
Reset task structure (WBS)
Change structure builders
Adjust the structure builders and click "Save". The task structure is rebuilt accordingly.
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.
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.
For example, let's generate a hierarchy resembling how data is presented on a Trello Board - task are organized into lists on the BigPicture Power-Up Public Roadmap:
To generate such a hierarchy, enable the ‘Boards' and 'Lists’.
As a result, tasks are organized just as on the Trello board.
Task edition blocked in Jira
When task editing is blocked in Jira, a task can be moved in the BigPicture WBS structure. Task position in WBS can be changed if it doesn't result in any changes in Jira.
Tasks can be moved:
Vertically (up or down in the tree structure)
Horizontal (indent level can be changed)
Exception:
If the automatic WBS rules are in place and a change of a task position would require a change of task fields, the indentation is blocked.