Scrum user and EAP read-only users cannot read rm_story records in AustraliaDescriptionEAP read-only users (sn_apw_advanced.eap_read_only) are unable to read rm_story records due to the deprecation of the com.snc.agile_read_roles plugins in Australia. Additionally, from Strategic planning version 4.14.0 onward, Agile Development 2.0 users (scrum_user) are unable to view rm_story records. Steps to Reproduce Scenario 1 — scrum user: Impersonate a user with the scrum_user role.Open the Agile board, or open an rm_story record directly.Observe that records are not fully loaded — the form is partially loaded with less information than expected. Scenario 2 — EAP read-only user: Impersonate an EAP read-only user (sn_apw_advanced.eap_read_only).Go to the EAP backlog, select any agile team, and select Stories from the work item type dropdown.No stories are displayed, though the selected team's stories should appear.WorkaroundAn update set resolves this issue. The fix depends on the customer's currently installed version of Strategic Planning — identify the version first, then apply the matching update set: Strategic Planning < 4.14.0 → apply update set fix_rm_story_access_issue_v1.xmlStrategic Planning >= 4.14.0 and < 4.16.0 → apply update set fix_rm_story_access_issue_v2.xmlStrategic Planning >= 4.16.0 → no action needed; the fix is already included out of the box. Download the update set matching your version, then import and apply it. Try to reproduce the issue again — it should now be resolved.Related Problem: PRB2038687