Versions Compared

Key

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

...

You can create a Hierarchy using a simple Hierarchy editor.
To do this, go to Templates and select the Create Hierarchy in the navigation bar.

...

Fill the required Hierarchy name field and optionally add a Description.

...

2. The mandatory Owners field is filled in with the reporter name automatically. It is editable and have the multiple users select ability.

...

3. The Tag field is optional. You can create a new tag there or select the one you have created before.

...

4. The Alternative projects field is also optional. You can select one or several projects and they will be shown at the top of the projects list on the Manage Hierarchies page while the node editing. Follow the link https://appsdelivered.atlassian.net/wiki/spaces/SIT/pages/755335169/How+to+make+Temporary+Changes+before+Hierarchy+Apply+on+the+Manage+Hierarchies+page#How-to-use-ALTERNATIVE-PROJECTS-funtcion for more information.

...

...

The Variables section is optional. You can create variables there and use them in the following hierarchy nodes

...

There are two types varaibles avialable on the Create Hierarchy and Edit Hierarchy pages:

...

  • Enter the version value into the Name field. Provide the default value like 1.1.1.

  • Click the Add button placed in the Variables section once more.

  • Select the USER type for the second variable in the Type field instead of TEXT type.

  • Enter the name value into the Name field of the second variable.

  • Start typing the admin name and select the admin from the list of users in the Name field of the second variable.

...

6. Click the Add Node button at the bottom of the Nodes section to create your first Root Node.

...

7. For the newly created Root Node, you need to fill out the Summary of the future issue, choose the Project in which it will be created and the appropriate Issue Type. For demonstration, I will enter the ‘Node for $name in the $version’ value into the Summary field.

...

8. Enabled Dynamic Reporter checkbox setsthe Reporter field to be equal to any user that’s applying the hierarchy. It is checked by default. In case you want to Disable it please select a fixed user as a Reporter when applying the Hierarchy.

...

9. Enabled Active checkbox means that the following Node will be applied after clicking the Apply button on the Manage Hierarchies page. Follow the link Active and Inactive Nodes for more information.

...

10. Click the Ready button on the created Root Node to complete the preparation of the Node.

...

11. Now you can proceed with filling in the fields of the future issue. Click the Edit Fields button.

...

Additionally, you can use the Template Picker that is located in the upper right corner of the dialog to simplify filling out the fields in case you already have some Templates.

...

12. When the issue is ready, click the Apply button to save its state and continue working on creating a Hierarchy.

13. Click the Add Child on the created Root Node to create the nested Child Node. Repeat the steps to populate the Root Node and populate the Issue for the nested Node.

...

14. Create Nodes for all the issues you need, related to this Hierarchy. You can mix different projects and issue types within a single Hierarchy.

...

15. Click the Validate button to check the Hierarchy on errors. If everything is set up correctly, in the Validation column for each Node there will be a

Status
colourGreen
titleValid
status displayed​.

...

16. Now you can save the Hierarchy using the Save Hierarchy button at the bottom.

...