"We couldn't connect to that work item." - issue loading tasks

[Wojciech Kosmala]

For the last couple of weeks, around 1/3 of the tasks I open result in the following error:

We couldn't connect to that work item.

Make sure that this work item actually exists in that space. If it does, try again in a few minutes. If you still can't link to the work item, contact your Jira admin.

Upon 2nd, sometimes 3rd try, they open fine.

I've already tried:

- connecting to a different Wi-Fi

- clearing cache

- removing cookies

- relogging to Atlassian

[D]

Stumbled upon same error, it seems when you have custom field and new project this is popping up. Just create a new scrum project and first issue you will get this issue if you have custom field created and assigned to default view.

JS error:

fetchIssueAggData.tsx:179 Uncaught (in promise) RelayNetwork: No data returned for operation `mainIssueAggQuery`, got error(s):
Validation error (FieldsConflict) : 'jira/issueByKey/fields/edges/node/fieldConfig' : returns different types 'JiraFieldConfig' and 'null'
Validation error (UnknownType@[jira/issueByKey/fields/edges/node]) : Unknown type 'JiraServiceManagementSlaField'

See the error `source` property for more information.
at r (34:104:230855)
at Object.create (34:104:231150)
at 34:104:216494
at Array.forEach (<anonymous>)
at t._handleErrorResponse (34:104:216258)
at t._handleNext (34:104:217285)
at 34:104:216052
at e.exports (34:104:231565)
at 34:104:216037
at 34:104:215359
at index.ts:29:4
at Object.E (34:107:246192)
at Object.schedule (index.ts:27:19)
at 34:104:215335
at 34:104:169079
at t.subscribe (34:104:169123)
at t._schedule (34:104:215439)
at t._next (34:104:216010)
at Object.next (34:104:213748)
at Object.next (34:104:168839)
at Object.next (34:104:167892)
at Object.next (34:104:168839)
at h (multi-fetch.ts:139:5)
at Object.next (multi-fetch.ts:286:7)
at Object.next (34:104:168839)
at index.ts:126:2

shared~vendor~stable~ar.c97a8480.js:2 n: Validation error (FieldsConflict) : 'jira/issueByKey/fields/edges/node/fieldConfig' : returns different types 'JiraFieldConfig' and 'null'
at c (IssueViewCriticalQue…Preloader.tsx:86:16)
at d (IssueViewCriticalQue…reloader.tsx:145:40)
at to (shared~vendor~stable….c97a8480.js:2:4436)
at W.port1.onmessage (shared~vendor~stable….c97a8480.js:2:3196)

 It is being reported to https://xxx.atlassian.net/rest/internal/2/log/safe/error 
Hope someone looks at i

[D]

Overall I see many UI issues, probably some failed release :) 

[Leigh Rushworth]

Hi, we've troubleshot this issue and for us it was related to the parent work items being in a resolved / done state.  Where the parent work item had a status change that triggered the automation to set it to a done state, but it still had unresolved child / linked work items it wouldn't open them correctly displaying the 'We couldn't connect to the work item' message.  Troubleshoot with two screens with alternate browsers helps.  I used MS Edge, Chrome and Safari (Mac).  It took a while :).  Look for resolved work items that appear with a Strikethrough font and reset their status to an Unresolved / Open state.  Hopefully this fixes the issue.  It has for us. 

[Shalini Pradhan]

Hello @Wojciech Kosmala ,

Good day! Welcome to Atlassian Community :)

Could you please tell us if this is happening only on your user account? I understand you have tried few troubleshooting steps, but I would request you to try out the following action plan step by step and see if that helps

Clear browser cache and cookies

1. Log out of your Atlassian account.
2. Clear all browser cache and cookies, not just cookies.
3. Log in to your Atlassian account and try to access Jira again and access the issues
4. Try in incognito mode as well

Disable all browser extensions and add-ons

1. Disable all browser extensions and add-ons.
2. Try to access Jira again and access the issues

Check for firewall

If your device or network has a firewall setup, I would request you to check if they have allowed connection to Atlassian's IP addresses. You can refer to the following document for more details:

• IP addresses and domains for Atlassian cloud products.

Allow 3rd party cookies

I would request you to follow the below steps (The steps are for Chrome but should be similar for other browsers):

1. Go to Chrome settings.
2. Go to Privacy and Security.
3. Click on Third-party cookies.
4. Select Allow third-party cookies.
5. Restart the browser and try to access Jira again.

Additionally, please ensure that you are using the latest version of one of the supported browsers listed here.

Thank you!

[Valerie Knapp]

Hi @Wojciech Kosmala , welcome to the Atlassian Community and thanks for your post.

Are you the only person using your site that has this problem?

A site to bookmark, if you haven't already, is this one - https://jira-software.status.atlassian.com/ . There have been some incidents recently impacting Jira, so it might be related to that, if you weren't having this problem before.

It sounds like you have tried already the standard troubleshooting solutions. I wanted to write because I was curious if others trying to use the Jira site are also experiencing this.

I look forward to your reply.

Best wishes

[Wojciech Kosmala]

There's at least 1 person seeing similiar errors in our company

[Valerie Knapp]

Hi @Wojciech Kosmala , thank you for your reply.

It sounds like this is a site-specific issue so I would ask that you report it to the service desk - https://support.atlassian.com/contact/ 

I have also flagged this post to Atlassian but the ticket would be the correct route so they can get the details of your site, etc.

Best wishes

[Leigh Rushworth]

We're also experiencing this issue, exactly as described above.  Multiple users.

[Matt Brown]

I'm getting this error with a specific issue that has sub tasks.  I can see the issue when I search the list view and the sub-tasks still have it as their parent, but when I go to view it I get the issue described above.

[Jared Cross]

We are having this same issue today.

All subtasks are unavailable with the "We couldn't connect to that work item." message.

I see from the status page at https://jira-software.status.atlassian.com that there was an incident earlier today (10/27/2025) that was apparently resolved, but this issue is ongoing if it was related to that status incident.

[Valerie Knapp]

Hi @Jared Cross , thanks for your post. There is still an active incident - https://status.atlassian.com/ so please keep an eye on status page for when it is resolved.

Sorry!

[Alex Thompson]

I just started experiencing this issue - I get the We couldn't connect to that work item. error on every task.

I also have access to two other company's Jira boards and get the same error there.

On the iOS app I see the following error:

Validation error (FieldsConflict) : 'jira/issueById/fields/edges/node/fieldConfig' : returns different types 'JiraFieldConfig' and 'null'

It does this for all three company boards I have access to on the app.

I assume this is a system wide Atlassian issue or has something gone wrong with my own login account?

[Nate Sturgess]

Me too. 

I have tried incognito and a bunch of other things and all to the same result. 

Must be Atlassian!

[Admin MPR]

I have the same issue, all started 10 minutes ago. @Shalini Pradhan maybe you can help us?

[Anna Pin]

Same and same. Assuming a global Atlassian issue right now

[Charvin Kale Peñaverde]

I’ve already tried using different browsers, such as Edge, and I even tried logging out to see if it was an account issue, but the problem persists. Hopefully, it can be fixed right away

[Mirela Wohlford]

I am experiencing the same issue across all JIRA work accounts, I cannot open any tasks: "We couldn't connect to that work item.

Make sure that this work item actually exists in that space. If it does, try again in a few minutes. If you still can't link to the work item, contact your Jira admin.”

So it does not appear isolated to one browser, project, or permission set. 

[Bryan Casey]

Same here... "Make sure that this work item actually exists in that space. If it does, try again in a few minutes. If you still can't link to the work item, contact your Jira admin."

Messaging so Atlassian are aware of this issue

[Mirela Wohlford]

Mystery solved, tried contacting support: "Our support system is experiencing a technical issue. During this time, you can create support requests and reply to existing tickets via email, but these will only be visible to our Support team when our system is back online." 

[Alexey Kharitonov]

Log in/out, different WiFi, different browser/OS, nothing helps.