After migrating a Custom Page or Custom HTML App built on App SDK to a Custom View, notes, status text, or report-out fields entered by one user may continue to appear only for that user. Other viewers of the shared dashboard, including admins(Project, leadship), see the field blank or unchanged, even though the original author still sees the entry after reloading the page
This article explains how to configure a Custom HTML widget code & ensure report data is visible to all users in a workspace by saving content to a Rally object instead of the browser's local storage.
Product -
Any custom app's save logic writes data using Rally.data.PreferenceManager, with a fallback to the browser's localStorage when the preference write doesn't succeed (or the app is coded to prefer local storage). localStorage is scoped to one browser, one user, and one origin. It is never sent to the Rally server and is never visible to any other user's session. As a result, only the browser that made the original entry ever shows that data; every other viewer of the same page sees nothing.
Workaround:
The new Rally Widgets fix requires rebuilding the app as a Custom HTML Widget within a Custom View. Since Custom HTML Widgets cannot access Rally.data.PreferenceManager, you must persist data centrally by writing it directly to a Rally object via WSAPI, this ensures that every viewer reads the same server-side value.
c_ReportOutData.updateWsapiObject and fetchWsapiObject.c_ReportOutData field on the currently selected Release.