Skip to main content
Back to Kantata.com Blog Tour Status

Task Hierarchy in Insights

By David Forsythe | Updated

Learn how to reproduce the Task Tracker order in Insights using a prefix in task names

 
Permissions Needed: Access Groups: Insights - OR - Reports Viewer (or higher) and Insights Can Edit permission

Due to the underlying data, tasks in Insights cannot be sorted by their WBS order using the sort column button. However, you can reproduce the Task Tracker order in Insights by using a prefix in task names.

  1. In Task Tracker, sort the tasks as you desire.
  2. Edit the name of each task and add a prefix at the beginning in the following format: 1.0.0.0.0. The prefix should have as many digits as there are levels in the project’s Task Tracker (up to 5 levels deep).

    You can use the WBS column as a reference. For example, in a project that goes 4 levels deep, the task with WBS number 1 would be prefixed with 1.0.0.0. The first subtask of that task would have a WBS number of 1.1 and would be prefixed with 1.1.0.0. The second subtask would have a WBS number of 1.2 and would be prefixed with 1.2.0.0.

    Leading zeros should also be included in the prefix. If there are more than 10 tasks in a level, add one leading zero. For example, 01.00.00.00. If there are more than 100 tasks in a level, add two leading zeroes. For example, 001.000.000.000.

    Refer to the screenshot below for an example.
    task tracker for task hierarchy in insights v2.png
  3. Allow Insights to refresh.
  4. Create a custom report.
  5. Use the Task: Title Aggregate attribute instead of Task: Name to display task names. This will allow tasks to be sorted alphabetically.
    task hierarchy in insights custom report3.png

NOTE

  • If tasks are reordered, archived, or deleted, the prefix must be updated. For instance, if a task named 2.0.0 Discovery is moved above a task named 1.0.0 Kickoff, the tasks must be renamed to 1.0.0 Discovery and 2.0.0 Kickoff. 
  • If a subtask of a new depth is added, all the prefixes must have another digit added. For example, if a project has tasks up to 3 levels deep and the prefixes are N.N.N, then a task that is 4 levels deep is added, all the prefixes must be updated to N.N.N.N.

 

Related Articles

Insights Dynamic Dashboards

Standard Dashboards

Custom Dashboards and Reports

Related Articles

Insights Classic

Standard Dashboards

Custom Dashboards

Custom Reports

Kantata OX API

By David Forsythe
Join us at Kantata!
Return to top