500 error when enabling the Sprints feature in a team-managed project (PUT /rest/agile/latest/board/

[Giles Fokam]

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?

[Marc -Devoteam-]

Hi @Giles Fokam 

Is the space a Team Managed psace based on the Scrum template, as this is required to be the space type?

To use the feature a backlog must be available.

[Giles Fokam]

Hi Marc, thanks! It's a team-managed Software space created from the Kanban template, and the Backlog feature IS already enabled (Backlog view works fine on the board). Per the docs, turning on Sprints in a team-managed space is supported from that state (it converts the board to scrum-style). The failure isn't a validation message either - the toggle's PUT to /rest/agile/latest/board/{id}/features returns HTTP 500 with an internal java.lang.IllegalAccessException referencing ContainerNavigationQueryOperations, which is why it looks like a server-side regression rather than a missing prerequisite. Also reproduces on a freshly created space on the same site.

[Marc -Devoteam-]

Hi @Giles Fokam 

I can reproduce your issue.

Raise this with Atlassian Support, as this might be a BUG.

[Marc -Devoteam-]

I also requested assistance from Atlassian on this post.

[Giles Fokam]

Thanks a lot for confirming the repro and for flagging Atlassian on this, Marc - much appreciated. I'll keep this thread updated with anything we learn from our side.

[Anastasiia Dimnych]

Hi @Giles Fokam,

I understand this issue must be frustrating for you. I've created a support ticket on your behalf - JST-1335619. Please keep an eye on your email for updates, and we're here to help you through this.

Best regards,

Anastasiia

[VRodriguesSilva]

@Anastasiia Dimnych  I'm also having the exact same problem. Is this a general bug then?