Inconsistent Behavior while Deleting Predecessor in Task Timeline view

Products

• Clarity PPM SaaS
• Clarity FedRAMP
• Clarity PPM On Premise

Issue/Introduction

When you have a list of Tasks in the WBS where some tasks are in a collapsed section and are not visible on the Timeline, the Task Dependency line is not visible as expected, however, the 'Predecessor' and 'Successor' columns still show the virtual 'WBS' or 'Row' number. This can cause issues for updating the data in these fields resulting in inconsistent behavior

Steps to Reproduce: 

1. Login to Clarity MUX
2. Create a Task hierarchy that looks like this
   • A
     • A1 
   • B
     • B2
3. Create a dependency from A-1 to B-2
4. Add the "Predecessors" column to the Gantt layout
5. Collapse "A"
6. Try and delete the predecessor for task "B-2" using the predecessor column

Expected Results: The 'Predecessor' and 'Successor' columns should not include a virtual number reference for any dependent task that is NOT VISIBLE on the Timeline due to collapsed sections or filtered results. 

Actual Results: The fields show a virtual number for all dependent tasks and performing an update causes incorrect outcomes in trying to delete the dependent task.

Environment

Clarity 16.3.3, 16.4.0,16.4.1

 

Cause

DE179681

Resolution

When the Task Timeline has collapsed sections or a filtered list where the dependent task is not visible on the page, the 'Predecessor' and 'Successor' columns will NOT show a 'WBS' or 'Row' virtual number reference, which is now consistent with NOT displaying the task dependency line for the same list of tasks. All dependent tasks are available in the Task 'Dependencies' flyout sub-tab. 

Fixed in

• Clarity 16.4.2 
  
  

Workaround: When using collapsed sections or looking at a filtered list, use the Task 'Dependencies' tab flyout, which lists ALL dependent tasks for that row.