Status report string values are not copied over when published if the view is changed`

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

SUMMARY OF DEFECT
String values in a draft Status Reports are not copied to the Final version after publish if the view used while publishing 
does not have the string attributes.  

STEPS TO REPRODUCE
1. Navigate to MUX - Projects
2. Open a Project - Status Reports
3. In Status Reports - Preview, create a view with the below String fields
   Schedule Explanation
   Upcoming Activities
4. Input value for the above String attributes and make sure the value is saved
5. Create a new view which does not have the above string attributes in it. 
6. Select that view and then Publish the Status Report

Expected: The newly created (Draft) Status report has values for Schedule Explanation and Upcoming Activities which was saved 
          in Step 4

Actual: Schedule Explanation and Upcoming Activities fields are blank in the newly created draft version.           

Workaround: Change the view which has the string attributes and then publish the report.

Environment

16.3.3

Resolution

This is working as per the design because the copy of fields from one Status Report to the other is using API calls and not backend copy. Hence only the fields in the view will be copied over.