MUX - Inconsistencies with Status Report ID field when auto-numbering is enabled.
search cancel

MUX - Inconsistencies with Status Report ID field when auto-numbering is enabled.

book

Article ID: 275820

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

When first navigating to Status tab when no previous status reports were created the ID will be assigned as something like this SR_2023-11-06 16:11:15 and report status will be in Draft. After publishing this report the next draft report that is populated will have auto-number ID as defined in Studio. If all status reports in the list are in Final status the next time user clicks on the Status tab the status report will be created in Draft status with SR_2023-11-06 16:11:15 id.  After publishing this report the next draft report that is populated will have auto-number ID as defined in Studio.

 

Steps to Reproduce: 

1. In Studio enable auto-numbering for ID attribute on status report object.
2. Navigate to MUX->Projects and open or create any project.
3. Click on Status tab (if not seen add it via project blueprint).
4. After preview/publish status report notice the ID field value it will be in this format SR_2023-11-07 13:11:05.
5. On the consecutive status report it will pick auto-number scheme as defined in the studio.
6. When All status reports are in Final status next Draft instance will again choose this format SR_2023-11-07 13:11:05.

Expected Results: It should be using auto-numbering for all use cases mentioned in the STRs.

Actual Results: It is not always creates status reports with auto-numbering scheme.

Resolution

DE78382, Fixed in 16.2.1.