We’d Love Your Feedback on Project Status Reports in the Next Experience

[HayleyAlexander]

Hello everyone! 
I’m Hayley Alexander, Inbound Product Manager for Project Workspace here at ServiceNow.

We’re continuing to evolve the Next Experience for Project Status Reports, and I’d love to hear directly from you about how you’re currently using them.

Specifically, I’m looking to understand:

• How your teams are creating, managing, and delivering project status reports today

• What’s working well in the current experience

• Current pain-points you're experiencing

Your feedback will help us shape upcoming improvements and ensure the experience fits seamlessly into how your teams work.

If you’re using (or have recently started using) the Next Experience Project Status Reports, please reply to this post. I’ll reach out directly to set up a short follow-up conversation.

Thank you for helping us make Project Workspace even better!

-Hayley Alexander

[Alpa82]

Hello @HayleyAlexander 

Currently, status report templates cannot be restricted to specific teamspaces (this is what we were told).
This lack of configuration means the global default template is applied to all teamspaces, when the status report is created via the related list.
I would like to request to consider the ability to define template visibility per teamspace / define default template for each teamspace. This would ensure that when a status report is created, only the relevant, team-space-specific template is utilised, maintaining data integrity.

In a summary:

• Current State: One-size-fits-all default template.

• The Conflict: Teamspaces have unique status report requirements (different fields on the status report)

Thank you

A.

[HayleyAlexander]

Hello @Alpa82 Are you currently using the legacy system status reporting? If you're on the next experience status reporting, you're able to create custom status reports templates across different teams and projects. 
If you have any further questions, I can reach out via DM. 

https://www.servicenow.com/community/spm-articles/status-reports-in-project-workspace-templates-and-...

[dsweet]

Hi @HayleyAlexander , our organization just upgraded the ServiceNow test environment to Zurich from Yokohama in preparation to upgrade the prod environment.  Couple of items for your feedback/help.

1. You had demoed a feature within the Project Details view to "Allow edit of status report on Project Workspace", is there certain user access required to enable that field/feature? I am unable to see it.

2. When creating a Status Report, and entering comments on the Budget, Resources, Schedule and Scope indicators, html tags are appearing in the fields, and this was also an issue in Yokohama (see screen capture below).

Thank you.

[chrisnicula]

I echo dsweet's 2nd comment.  Also, the functionality seems like a regression compared to the classic status reports.  1.  We use the out of the box functionality that shows only open RIDAC items but the ability to click a tab to view completed one.  Now the out of the box report in the Next Experience just shows all.  2.  Also, the decimal precision keeps blown out unnecessarily.  3.  The colors and general look were removed making this look like a draft and not a published status report.  We intend to keep using the classic status report due to these reasons.