v1.6.0How to make Temporary Changes before Apply Hierarchy

Temporary Hierarchy allows to make temporary changes in the content of your future issues right before applying hierarchies without making changes to the actual hierarchy.

This feature enables users to dynamically specify field values that cannot be imported to the Node details because of their dynamic nature ( I.e. a Hierarchy that generates issues for processing new hire might leave new person’s name empty in the Node and fill it in in the Temporary Hierarchy)

To use Temporary Hierarchy:

1. Click the Summary of the Node that should be edited

2. Make necessary changes in the issue fields

3. Click Apply button

After applying, the message “Hierarchy has temporary changes” would be displayed next to the Apply button.

When Temporary Hierarchy is applied, the issues will contain your temporary changes, while the Hierarchy itself will not be changed.

How to disable Hierarchy Nodes

Disable Hierarchy Nodes is a convenient tool that is useful in case you need to make changes to a Hierarchy on the go without spending too much time on it. For instance, there is a Hierarchy for a daily meeting, and one of the team members cannot be present. Instead of editing the entire Hierarchy you can exclude that one particular Node which you created for the user who cannot participate in the meeting and proceed with the meeting.

Open

Open

To exclude one or more members from the “Daily Standup” Hierarchy, you simply have to select nodes you want to exclude in the very last column of the table by clicking on the appropriate checkbox. Notice that as soon as you click on the checkbox of your choice the notification under the Hierarchy name in the upper left corner of the window will pop up. It will contain a “Hierarchy has temporary changes” message so that you will know for sure that there are changes to be applied.

You will see the message from the picture above every time you bring changes to the Hierarchy.

Now, when you have selected the Nodes or Hierarchies you want to exclude, you need to click the “Apply” which is located in the upper left corner of the application window, just below the name of the Hierarchy you are working with. When you click that button a “Confirmation” window will pop up where you will have to click “Confirm” to apply the changes you want to make.

Also, if you need you can edit the existing nodes on the fly. To do that, you simply need to click on the name of the Node or a Hierarchy you want to edit, after that the editing window will pop up where you can add any changes to the chosen Node you need.

There is one more thing you have to bear in mind. You cannot leave “Sub-task” nodes without their parent nodes in the Hierarchy. In case if you try to do so, all of the Sub-task child nodes will be excluded along with their parent nodes. Here is a step-by-step explanation of what would happen.

In the image above you can see that we have created a Hierarchy that consists of an Epic, one sub-task which is a child of that Epic, a Story and a Task, each of which has two sub-tasks. To exclude one or more nodes from the Hierarchy, we need to select them in the very last column of the table with a check box, just as we did in the picture below (if you select a parent node, all of its child nodes will get selected automatically).

Now, when we have selected the nodes we want to exclude, we should click the “Apply” button, located in the upper left corner of the application window. When we do so, the “Confirmation” window will appear with information on how many issues we are about to create.

We click the “Confirm” button and now we can see that the table has changed. We have all the same nodes except now we don’t have an Epic and a sub-task which belonged to that Epic.

As it was mentioned above, you cannot create any sub-tasks without a parent node. In the picture below, we tried to exclude all of the parent nodes, however, “Apply” button goes inactive every time we try to implement changes that are impossible to make.

In the picture below we have tried to exclude the Story node (Development), however, the SIT offers us to create only 3 issues, as defined in the “Confirmation” window. It happens so because “Dev. Back-end” and “Dev. Front-end” tasks don’t have a parent node anymore and thus cannot exist.

We click the “Confirm” button and proceed to the screen where we can find all of the issues we have created. As you can see only the issues which had a parent node were created, while other issues were simply excluded.