Jira Cloud – Team-managed project Board and JQL pages fail to load – TBT / Board ID 15 / Hash O2Z7FE

[Hakan AKIN]

Hello Atlassian Support,

We have been experiencing a critical Jira Cloud issue continuously since Friday, 31 July 2026.

Site: it.atlassian.net
Project: TBT
Project type: Team-managed
Board ID: 15

Affected URL:

Since 31 July 2026, the Jira board and JQL/Issue Search pages have not been loading. Jira displays the “Something’s gone wrong” error page.

Error hash: O2Z7FE

The issue is still ongoing as of 3 August 2026 and is blocking users from accessing boards, running JQL queries, and managing issues.

Main browser console error:

Error: issueTypeId is required for team managed workflow URL
Component: ManageWorkflowsMenuItem.tsx

Please investigate:

1. Whether the TBT team-managed project has missing or inconsistent issue type/workflow metadata.
2. Why ManageWorkflowsMenuItem is being rendered without an issueTypeId.
3. Whether a Jira Cloud frontend rollout or tenant-specific feature flag released around 31 July 2026 caused this issue.
4. Whether there is a tenant-side backend error associated with hash O2Z7FE.
5. Whether the affected feature flag or rollout can be reset or disabled for our tenant.

The problem has been ongoing for multiple business days and is significantly affecting our operations. We kindly request that this ticket be treated as urgent.

We can provide HAR files, browser console logs, screenshots, and network request details.

Regards,

[Gor Greyan]

Hi @Hakan AKIN

Welcome to the Atlassian Community!

Thanks for providing such a detailed description of the issue.

From what you've shared, this looks like a tenant-specific problem rather than something that can be diagnosed from the Atlassian Community. Community members don't have access to your Jira Cloud site, feature flags, backend logs, or the error hash, so we can't verify what's causing the "Something's gone wrong" page.

Since the problem is affecting core functionality (boards, JQL search, and issue management) and has been ongoing for several days, I'd recommend opening a support ticket with Atlassian if you haven't already. 

https://support.atlassian.com/

[Hakan AKIN]

Hi @Gor Greyan 

Thank you for your response and guidance.

We will open a formal support ticket with Atlassian and share the relevant error hash, timestamps, screenshots, HAR file, and console logs for tenant-level investigation.

Since the issue has been ongoing since Friday and is affecting boards, JQL search, and issue management, we will request an urgent review from the Atlassian Support team.

Thank you again for your help.

[Gor Greyan]

Hi @Hakan AKIN

Great!

Also, kindly ask you to accept the answer if it helped you.

[Thanasis Nikolaou]

Hey @Hakan AKIN 

The reply above is right that flags, the error hash, and tenant rollouts (your points 3–5) need a support ticket — file it at support.atlassian.com/contact with the HAR attached. But points 1–2 you can partly check yourself, and that console error is a decent clue: in team-managed projects each issue type carries its own workflow, so a crash in ManageWorkflowsMenuItem usually means one issue type's metadata is broken.

• Go to Project settings → Issue types directly (skip the board). Click through each type — if one errors or looks empty, that's your suspect. Was any issue type added or deleted around 31 July?
• Hit https://it.atlassian.net/rest/api/3/project/TBT in a browser tab and eyeball the issueTypes array for anything odd or duplicated.
• Try incognito or another browser — a stale JS bundle after a frontend rollout produces exactly this kind of crash.
• Rule out the boring cause too: TMP boards over ~5,000 issues throw the same generic error page (KB here), though your console error doesn't really match that pattern.

If the settings page confirms a broken issue type, adding a fresh throwaway type sometimes regenerates the mapping — worth trying before support gets to you.