| Info |
|---|
To Edit Hierarchy |
...
you need to open the Hierarchy Editor - ‘Edit Hierarchy’ page where you can update your Hierarchy |
Hierarchy Meta
Hierarchy Meta dialog is designed for the:
Editing Hierarchy name
Adding Hierarchy description
Changing owner (if you have available permissions for changing owner for the Hierarchy)
Categorizing Hierarchy by Tags
...
Field Name | Description |
|---|---|
Hierarchy Name | Name, up to |
60 characters long |
Description |
Optional description or notes about this Hierarchy for the other users.
Nodes Table
...
Optionally add a description to explain the hierarchy’s purpose. | |
Owner | Ability to change Owner for the Hierarchy. It`s available if you have available permissions for changing Hierarchy owner |
Tags | Add tags to categorize and organize hierarchies for easy filtering. |
...
Hierarchy Nodes Management
You can easily move, duplicate, or bulk edit nodes within your hierarchy.
Use the action buttons next to each node to move, copy, or delete.
For bulk actions, select multiple nodes and apply changes all at once.
...
Column name | Description |
|---|---|
Bulk changes | Apply actions to multiple hierarchy nodes simultaneously. |
Node Key | A unique |
identifier |
for each node, generated automatically by the add-on |
. |
Summary |
A brief summary or title for the issue represented by the node. | |
Project | The project in which the issue will be created. |
Issue Type |
The type of |
Assignee
An assignee of the future issue
Dynamic Reporter
A checkbox that controls the Reporter field in a future issue.
Checked - Reporter is always set to a current user
Unchecked - Reporter is specified in the Node or a current user (in a case when the current user has no Modify Reporter permission in the Node’s project)
Validation
Current Validation Status
Error Messages Area
issue the node represents. Supports all custom hierarchy levels (e.g., Company, Initiative, Department, etc.). | |
Assignee | The person responsible for the issue associated with the node. |
...
Actions | Description |
Add child | Add a node under the current node. The child node will be positioned according to the hierarchy structure you’ve defined, maintaining the appropriate parent-child relationship within your custom setup. |
Duplicate | Create an identical copy of the hierarchy node, including all its child nodes, if any. |
Move out | Reassign the node to a different parent node within the hierarchy, while maintaining the integrity of your hierarchy structure. |
Move up/down | Adjust the position of the node within its current hierarchy level. This allows for flexible reordering based on your project needs. |
Delete | Remove the node from the hierarchy, which will also remove any associated child nodes. |
Validation Statuses
Validation status | Description |
|---|
 |
| Newly created Node |
| Status | ||||
|---|---|---|---|---|
|
| No field values have been specified for the Node |
| Status | ||||
|---|---|---|---|---|
|
 | All the required issue fields have been set |
| Status | ||||
|---|---|---|---|---|
|
The Node has been updated but hasn’t been validated yet
| Status | ||||
|---|---|---|---|---|
|
The Node has successfully passed the validation and is ready to be used by the current user
| Status | ||||
|---|---|---|---|---|
|
The Node is causing structural problems or is missing required fields.
...
Action Buttons
Buttons | Description |
|---|---|
Hierarchy | |
Add Node | Creates a Root Node for the new set of related issues |
Validation
Validates each Node in the Hierarchy and the Hierarchy overall
Save Hierarchy
Update Hierarchy | Saves a Hierarchy that has been already validated |
Nodes
New Node
Ready
Save current Node configuration
Delete
Delete Node from the Hierarchy
Node (view mode)
Edit Fields
Open a dialog that allows one to populate issue fields and save them.
Add Child
Add a Node under the current Node. If current Node is of type Epic, the Child Node becomes either included in the Epic (for Nodes with standard issue types) or becomes a Sub-task (for Nodes with sub-task issue types)
Actions
A set of actions for the Node
Actions → Edit
Edit Node details: Project, Issue Type or Summary
Actions → Copy
Create a deep copy of the current Node (including Child Nodes) under the same Parent Node (if any) or Root Node (if there’s no Parent Node)
Actions → Move
Open up a dialog that allows moving the Node within the Hierarchy.
Actions → Delete
Delete Node from the Hierarchy
 | Undoes or Redoes actions are taken with Hierarchy Nodes |
Node (edit mode) | |
Add | Save current Node settings |
| Revert any changes done to the Node since the last save |
Copying Nodes
Node copying allows one to quickly create repetitive or similar set of issues within your Hierarchy. To copy a Node, click Actions next to a corresponding Node, then select Copy in the dropdown menu. This would create a deep copy of the original Node and add it under the original Root or Parent Node. For convenience, copied Nodes are marked with a “Copy - “ keyword in their Summary.
Moving Nodes
...
To move a Node within a Hierarchy, click Actions button next to a corresponding Node, and select Move. This action opens up a Move dialog (see screenshot).
Under the Parent node please select a Node under which you’d like to move the current Node or select None in case current Node doesn’t need a Parent Node.
Under the Nearest node select a Node, which is located as close as possible to the desired position.
If Parent Node is not set to “None“ and there are no Child Nodes, then only the First Child option would be available under the Nearest node dropdown.Under Insert select the desired position relative to the Nearest node.
Click Move to perform the movement.
...