On our Jira Cloud Free site (new navigation UI), turning ON the Sprints feature in a team-managed Software project fails every time with the flag "Something's gone wrong - An error occurred on our end. Refresh the page and try again."
The underlying REST call returns HTTP 500:
PUT /rest/agile/latest/board/36/features with body {"boardId":36,"feature":"jsw.agility.sprints","enabling":true}
The 500 response body contains an internal java.lang.IllegalAccessException referencing ContainerNavigationQueryOperations, which looks related to the new navigation rollout.
What we have checked:
- Reproduces consistently across multiple days (first seen 26 July 2026), from both the UI toggle (Space settings > Features) and direct REST calls.
- Also reproduces on a freshly created team-managed project/board.
- Acting user is org admin + site admin; no marketplace apps involved.
- The "Standups" toggle on the same Features page works fine, so it is specific to the Sprints/Estimation board features.
- No related incident on status.atlassian.com and no matching public bug on jira.atlassian.com that we could find.
Is this a known regression of the new navigation? Is there any workaround to enable Sprints on a team-managed board while this is broken?
