Hierarchy Editor Fields
Field Name | Description |
|---|---|
Hierarchy Name | Name, up to 64 characters long |
Description | Optional description or notes about this Hierarchy for the other users. |
Nodes Table
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 |
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.
For any questions or feature requests contact us via Customer Portal Or drop us an email support@appsdelivered.atlasssian.net. If you are using this option, please check your junk folder regularly, as our reply can be placed there by your email service.
Before submitting a bug report or support ticket, please update to the latest version of the add-on.
Please add information about the version of Jira and the add-on.