Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Hierarchy Editor Fields

...

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.

  1. Use the action buttons next to each node to move, copy, or delete.

  2. 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

Node

identifier

(

for each node, generated automatically by the add-on

)

.

Summary

Summary of your future issue

A brief summary or title for the issue represented by the node.

Project

The project in which the issue will be created.

Issue Type

Issue

The 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

Action buttons

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

StatustitleNEW

image-20240319-232123.pngImage Added

Newly created Node

Status
colourRed
titleEMPTY

image-20240319-232036.pngImage Added

No field values have been specified for the Node

Status
colourGreen
titleFILLED
image-20240319-232156.pngImage Added

All the required issue fields have been set

Action Buttons

Buttons

Description

Hierarchy

Add Node

Creates a Root Node for the new set of related issues

Save

Update Hierarchy

Saves a Hierarchy that has been already validated

Image Removed
Image Added

Undoes or Redoes actions are taken with Hierarchy

Nodes

Nodes

Delete

Delete Node from the Hierarchy

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)

Node (edit mode)

Add

Save current Node settings

Cancel

image-20240319-234215.pngImage Added

Revert any changes done to the Node since the last save

...