Switching Between Views in MUX, marks the view as edited without user making any changes

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

Switching Between Views in Modern UX Marks the view as edited without user making any changes

Scenario 1:

STEPS TO REPRODUCE:

1. Login to Classic UI.
2. Create a Sub-Object of Project Object and create some dummy attributes on the object. It should be API enabled
3. Navigate to Modern UX.
4. Under Administration -> Blueprints -> make a copy and edit the Blueprint of Type "Project". Under modules add the Sub-Object module.
5.  Assign the Blueprint to a project. Open the project and navigate to Sub Object Module.
6. Create 4-5 instances.
7. Add 2 additional columns to the view and save the view as "Test View1".
8.  Add all the columns and save the view as "Test View2".
9. Change the sort order on Test View2 and save it.
10. Now change the view to "Test View1".

Expected Results : View is changed to "Test View1".
Actual Results : View is change to "(Copy) Test View1" without any change done to the columns.

 

Scenario 2:

STEPS TO REPRODUCE:

1. Navigate to Projects Grid.
2. From the 'Standard View', Save As a new view such as 'My Standard View - Project Name'. Note that this view sorts by Project Name - Ascending by default.
3. Modify the sorting of the view to Project ID - Ascending, and save the modified view to 'My Standard View - Project ID'.
4. Log out and log back in with the same user.
5. Navigate to Projects Grid. Current view in use is 'My Standard View - Project ID'.
6. Switch view to 'My Standard View - Project Name' and do not do any changes.

Expected Results: 'My Standard View - Project Name' is loaded normally.
Actual Results: 'My Standard View - Project Name' is loaded normally but displayed in italics, as an unsaved view. If the view is 'Shared' instead of 'Mine', when displayed as an unsaved view, the '(Copy)' prefix is also added before the name in italics [this would be expected for any 'Shared' unsaved view].

This is only occurring for the first time the view is loaded after login. Subsequent loads of that view will not make it unsaved.

Environment

Clarity 16.2.3, 16.3.0, 16.3.1

Cause

This is caused by DE154491

Resolution

Due to the code area affected and changes needed to address this issue, a user story has been submitted to implement the infrastructure work required.

This will be implemented on a future release