Edit Hierarchy
- Riley Venable
- Viktor Sapaiev (Deactivated)
- Anna Konovalova (Deactivated)
The Edit Hierarchy page can be opened from the Manage Hierarchies page of both Detailed and List Views.
To enter the Edit Hierarchy page from the Detailed View you have to click the Edit button below the specific Hierarchy name.
To open the Edit Hierarchy page from the List View you have to click the pencile image in the specific hierarchy row.
The ability to Edit Hierarchy is to be granted to the user on the Smart Issue Templates Permissions page.
The Edit Hierarchy page is the same as the Create Hierarchy page. All the fields are editable. Make the needed changes and to save them click the Update Hierarchy button at the footer of the Edit Hierarchy page.
The Edit Hierarchy page consists of 3 sections:
Hierarchy Details
Variables
Nodes
Edit Hierarchy Details
Field Name | Description |
|---|---|
Hierarchy Name | Mandatory Hierarchy Name, up to 64 characters long |
Description | Optional description or notes about this Hierarchy for the other users. |
Owners | Manadatory field that displays the Reporter name by default. Can contain multiple usernames. |
Tags | Â |
Alternative Projects | Â |
Variables section
Nodes section
Column name | Description |
|---|---|
Node | A unique Node identifier (generated by the add-on) |
Summary | Summary of your future issue |
Project | The project in which the issue will be created |
Issue Type | Issue type of future issue |
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 |
Validation Statuses
Validation status | Description |
|---|---|
NEW​ | Newly created Node |
EMPTY​ | No field values have been specified for the Node |
FILLED​ | All the required issue fields have been set |
UNCHECKED​ | The Node has been updated but hasn’t been validated yet |
VALID​ | The Node has successfully passed the validation and is ready to be used by the current user |
INVALID​ | The Node is causing structural problems or is missing required fields. |
Control 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 | 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 |
Node (edit mode) | |
Ready | Save current Node settings |
Cancel | Revert any changes done to the Node since the last save |
Actions button for nodes
The Actions button allows to make specific actions with the hierarch Nodes on the Create Hierarchy and Edit Hierarchy pages. Read more about it here.