| Table of Contents | ||||
|---|---|---|---|---|
|
...
The colors of the links help you to know what problems are contributing to the sum of the one issue.
Color | Line | Description |
|---|---|---|
Black |  | The issue does not contribute to the root issue (there is one outward link at least in the branch connecting the issue with the root which breaks the roll-up progress) |
Red |  | The issue contributes to the root (all the chain of linked issues are inward) and all their contributing children are already loaded in the hierarchy, therefore the total contribution of the branch under the issue is well known |
Orange |  | The issue contributes to the root from more than one way and each way does it partially with the same amount (balanced) |
Light red |  | The issue contributes to the root but not all its children have already be loaded, therefore the real total contribution of the branch is unknown as it might vary when more children are loaded |
Yellow |  | The same that the previous one when the issue contributes from more than one branch |
...
Progress Bars Colors and Individual progress of each issue
...
When an issue appears in several places contributing, all your appearances are shown with an orange link to indicate that the issue is contributing in different ways.
...
These cases are detected by "Links Hierarchy", and will mark the issues where it occurs with an orange border. You can review each case and decide if it is correct or not.
...
| Note |
|---|
Where is my custom field? A custom field will be shown in the menu, if it has value for at least one issue in the hierarchy displayed. Custom fields that can be displayed in the hierarchy are ONLY of a NUMERIC type. There is no need to add a customfield into the list as Links Hierarchy fills them into the list dynamicly (automatically). In other words Links Hierarchy take customfields from those issues that are present at the moment in hieararchy tree. PLEASE PAY ATTENTION: if issues on a particular hierarchy Depth level do not contain any numeric custom field - no custom field will be reflected in tree manu “Custom Field“ |
| Note |
|---|
Jira Cloud notes For reasons of efficiency, existing custom fields in the Jira Cloud instance and global time tracking settings, are read only once. So, if custom fields are created in the Jira Cloud instance (or time tracking settings 'Working hours per day', 'Working days per week' are modified), it will be necessary to clean the filters ("Reset configuration" option) for the app refreshing them. |
...