SPM - ProjectWorkspace: Status Reports

dsweet · 3 hours ago

When creating a status report within the Project Workspace using a customized report template, the Milestone Planned End date is not sorting as expected and is also sometimes set to the same date when duplicating a report. Also, the time is included in the milestone date, this used to be an editable field by setting the "Allow edit of status report on Project Workspace", now I am unable to edit this since the latest patch.

Currently using version MID buildstamp: zurich-07-01-2025__patch10-hotfix3-07-01-2026_07-02-2026_1215.

Please advise if there is a way to,

1. Update the Milestone details, format the date (Key Milestone/Planned end date

to remove the timestamp?

2. Can the Milestone Dates be sorted ascending by date (Key Milestone/Planned end date)

3. Look into why the dynamic Milestone Planned End Date (Key Milestone/Planned end date)

is set to the same date when duplicating the report.

4. I am unable to delete a row in the dynamic Milestones table, less functionality then previous.

Vikram Reddy · 2 hours ago

Hey @dsweet,

Two different things are stacked on top of each other here: the timestamp and duplicate-date behavior are a known defect, and the edit/delete lockout is almost certainly a report state issue, not a removed property.

Item                          Likely cause                                  What to do
1. Time shows on date field   Known defect - KB2809194 (dates showing       Log a case referencing KB2809194
                               full timestamps in SPM Project Workspace)
2. Milestones don't sort      Key Milestones list renders pm_project_task   No native sort control on the
                               rows in query/creation order, not end_date   template list; raise as enhancement
3. Same date on duplicate     Same underlying defect as #1, the copy        Track against KB2809194
                               snapshots the display value, not the field
4. Can't edit/delete rows     Report status likely = Published, which       Reopen/unpublish the report, then
                               ServiceNow locks read-only by design         confirm it_project_manager role

Milestones on a status report aren't their own record, they're rows on pm_project_task flagged milestone=true and checked as Key Milestone, and the date you're seeing is that task's end_date. There's no sort setting exposed on that related list in the template designer, so item 2 is just query order, not a sort bug you can flip a switch on.

I couldn't find any documented property named "Allow edit of status report on Project Workspace" in current docs or release notes for Zurich or Yokohama. What is documented is that a Published status report becomes read-only, with edit access otherwise gated by the it_project_manager role. That's the more likely explanation for 1 and 4 breaking after patch10-hotfix3, worth checking before assuming a property was deprecated.

References

Thank you,
Vikram Karety
Octigo Solutions INC

dsweet · 5m ago

Thanks Vikram for the quick reply, much appreciated. I will log a case against known defect KB2809194 for items for 1 and 3. Regarding item 2, I will also raise as an enhancement for the ability to sort milestones as this is a feature that should be available, nobody wants to look at milestones in a hap hazard order, especially steering committee members. Finally, something has changed if the functionality to edit the report since the hot fix. See the two attachements. Report is in Draft (this was not a feature previously) and secondly "Allow edit ..." is set to True.

Steps to Reproduce un-editable dynamic fields in the report

- Logged into ServiceNow Test Environment

- Navigate to the Project Workspace and select project.

- Navigate to Status Reports

- Created a new status report from template.

- Entered Exec Summary comments and test comments.

- Left status defaulted to Draft

- Selected Submit

- Navigated to Project Details and selected status reports

- Set “Allow edit of status report on Project Workspace” to True for newly created report above.

- Navigate back to the report that was newly created and attempted to edit the milestone fields and received message “Dynamic Fiedl: Values are Locked”

Note, non-dynamic fields are still editable, e.g. Executive Summary.