search cancel

Wrong partition displayed for Status Report List

book

Article ID: 228332

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

Classic UX Status Report List shows a fixed partition (always the same) regardless of the expected partition. However, the Status Report itself respects the view definitions for the expected partition.

Steps to Reproduce:

  1. Create a Partition Model with three partitions: 'All Organizations', and two children partitions, 'Business' and 'IT'.
  2. Add a resource as a partition member to all the partitions.
  3. For the object 'Project', set the newly created model as Partition Model.
  4. For the object 'Status Report', change the views for each partition, for both 'General' (e.g.: Layout: Edit) and 'Status Report List' (e.g.: Layout).
  5. Log out/log in with the partition member.
  6. Create three new projects, one for each partition.
  7. For the project in 'Business' partition, go to the Task list, then Options > Configure > General. Partition, as expected, will be 'Business'.
  8. Go to project Properties > Status Report then go to Options > Configure > General

Expected Results: Status Report List partition shows as 'Business', and shows the layout defined in 'Business' partition.
Actual Results: Status Report List partition shows as 'System', and shows the layout defined in 'System' partition.

  1. Create a new Status Report and open it.

Expected and Actual Results: The Status Report Create and Edit layouts show the layout set in the 'Business' partition for the Status Report object.

For an upgraded environment, instead of 'System' layout, the Status Report List layout seems to be stuck for all projects (in the same way, regardless of the partition of the project) to another value, like 'Business', unlike the Create/Edit views which will respect the partition.

Cause

This issue has been reported to Engineering as DE63169.

Environment

Release : 15.9.3

Component : CLARITY STUDIO

Resolution

This issue has been fixed in Clarity 16.0.1 and backported to 15.9.3 patch #3.