Grid Position Persistence Issue
search cancel

Grid Position Persistence Issue

book

Article ID: 429704

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity FedRAMP Clarity PPM SaaS

Issue/Introduction

In the project view, the configuration of the Staffing Grid (specifically the "Group By" headers and column alignment) fails to persist when navigating between sub-tabs. When a user sets a grouping (e.g., by Role) and navigates to another module returning to the "Staff" tab results in a layout discrepancy where headers or grouped rows do not render as they did initially

Steps to Reproduce: 

  1. Navigate to the Staff tab of a project (e.g., AI-based App Development).
  2. Apply Grouping: In the left-hand pane, ensure a "Group By" is active (e.g., Group by Role).
  3. Verify Initial State: Observe that "Staffing" and "Resource" headers are correctly aligned and the "Group By" rows (Business Analyst, Data Analyst, etc.) are visible.
  4. Change Context: Click on the any other tab
  5. Return: Click back on the Staff tab.

Actual Results: The UI component fails to reload the previous state correctly. Specifically:

  • The "Staffing" / "Resource" / "Totals" headers may shift or lose their association with the grid below.
  • The "Group By" toggle or row structure  appears inconsistent or requires a manual refresh to display correctly.

Expected Results: The Staffing grid should maintain its "Group By" state, column headers, and scroll position regardless of tab navigation within the same project.

 

Environment

Clarity 16.3.3, 16.4.1, 16.4.1 

 

Cause

DE182522

Resolution

Fixed in 16.4.2 

Additional Information

Additional improvement in pinning functionality is expected with 16.4.3 as described