Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Hierarchies allow users to create a set of related issues (i.e. Sub-tasks and Stories) in a matter of a few clicks.

ApplyHiearachyDemo.mp4

Hierarchies support all of the available issue types and custom fields, including even attachments (usually used to attach a document template).

Before creating your first Hierarchy we suggest making yourself familiar with key terms below.

Glossary

Hierarchy - a set of related Nodes

Node - a blueprint of an issue. It’s the main building block in the Hierarchy.

There’s a total of 3 Node types:

  • Child Node - a Node that is created under another Node (typically Sub-tasks or Stories under an Epic).

  • Parent Node - a Node that contains one or more associated Child Nodes

  • Root Node - a Node that doesn’t have any associated Parent Node


For any questions or feature requests contact us via the Customer Portal

Or drop us an email at support@appsdelivered.atlassian.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.

  • No labels