ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Task Timeline Second Column always show hierarchy

book

Article ID: 227488

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

In the modern ux for Task Timeline view If you change the order of columns i.e from NAME to the second position  to Start is on the second position and refresh the page, the hierarchy functionality is kept on the second column and ideally hierarchy should be shown on the Name column only irrespective of position.

STEPS TO REPRODUCE: 

  1. Login to clarity in the modern ux
  2. Navigate to Projects --> Task
  3. In the Task Timeline view drag Start or any column to second position
  4. Refresh the page or navigate to any other tab and come back to same task timeline


Expected Results: The hierarchy should be shown only on column NAME column and not to any other column 

Actual Results: The hierarchy is shown on any column which is placed at second position and not on Name

 

Cause

This was reported as defect DE63091 however after review this is considered as working as design. 

Environment

Release : 15.9.2, 15.9.3, 16.0

 

Resolution

The WBS Numbers are fixed and not configurable, the WBS Arrows will always be in the 2nd column because we don't want to lose the ability to see and use the WBS arrows regardless of the column configured - if we tied it to a specific field, then that could be a usability issue. The user could chose not to use the 'Name' field at all in the configuration and use something else, like the ID or Short Name or some custom field. The user also has the option to remove all columns in the configuration and will be left with the WBS numbers and the gantt bar chart area. In the Hierarchy Timeline, there is no WBS Column, so the hierarchical arrows will always be in the first column regardless of the field selected, for the same reason. 

Attachments