Advanced Roadmaps hierarchy levels
This feature is available for Cloud Hosting only.
As Worklogs support all Jira issues hierarchy levels, including Advanced Roadmaps, you can categorize or group your work logs by Legends, Initiatives, Epics, etc. You can view up to 10 hierarchy levels in our app. It allows you to analyze how the time was distributed toward the highest-level parent tasks.
Before you start using this feature, make sure you have created an Advanced Roadmaps plan, and added your Jira Issue Types which will be higher in the hierarchy than the standard Epic. You can learn more here.
Please note that whenever we use, for example, Hierarchy 2 in Worklogs, this refers to the Jira definition of Advanced Roadmaps, and all tickets marked with the number 2 in the JIRA configurations will be under Hierarchy number 2 in the app.
It is up to the Admin user to name the higher levels and their number in Jira issue type hierarchy. The Worklogs application will display all time logs for issues that have been added under the level.
Therefore, if you display, for example, hierarchy level 2 (in our case we named it as “Initiative”) in the Worklogs app the report will show you the time logged into Initiative itself and all linked Epics including their tasks and subtasks.
Displaying Hierarchies in the Worklogs app
We suggest displaying your hierarchies from higher levels to lower ones to make it easier to read the data.
You can maximally view 10 levels of your hierarchy. There are some examples below to help you understand how time logs are shown in the application.
For example 1 the time was logged for each hierarchy on November 13th.
For example 2 the time was logged into subtasks of hierarchy level 3.
Example 3 shows how work logs are presented when three levels of the hierarchy are displayed at once.
Example 1
In the first example, the hierarchy level 2 is displayed (Categorize by → Hierarchy Level 2).
At level 2 there are 3 hours logged.
At level 1 there are 4 hours logged.
Level 1 is lower in the hierarchy than level 2.
The report will show you a total of 7 hours. If you click on 7h in the report, you will see that actually these two levels have added up.
You may wonder why the report shows No value and 5h 20m.
No value is information regarding all levels above the given hierarchy you are currently displaying. Please bear in mind that No value will be also displayed for the hierarchies where no time was logged.
In this example, 8 levels of hierarchies are created, so in this case, No value will show the time logged from hierarchy number 3 to 8.
When you click on this time value, you will actually see all hierarchies above level 2 and how much time was logged there.
What remains to be explained is the logged time 12h 20m, which is marked as Total.
This is the sum of all logged time for all levels of the hierarchy.
When you click on this time value, you will actually see all hierarchies and how much time was logged there.
Summary
Below, you can see the same case, but with time logged for various days:
Example 2
In this example, hierarchy level 3 and its subtasks for which time was logged are displayed (Categorize by → Hierarchy Level 3, Group by → Subtasks).
In general, time was logged for several days in all hierarchies from levels 1 to 8.
There are two subtasks to which time was logged (45m and 1h).
In the image below there’s a description of how you should understand No value in such a scenario.
Example 3
In this example, hierarchies from level 3 to level 1 are displayed (Categorize by → Hierarchy Level 3, Group by → Hierarchy Level 2, Secondary Grouping → Hierarchy Level 1).
In general, time was logged for several days in all hierarchies from levels 1 to 8.
There are also two subtasks of the hierarchy level 3 with some time logged.
In the image below, it is described how the time of the currently displayed hierarchies is shown in the report.
In the next image, you can see how No value should be understood in this case.