Unable to link Epic to Atlassian Home Project

[bradley]

Environment Details:

Atlassian Cloud ecosystem — using Jira Software, Confluence, Product Discovery, and Atlassian Home (Teams / Goals / Projects).

Issue:

I’m trying to link a Jira Epic from a Jira Software Project to an Atlassian Home Project. Within Atlassian Home, each time I attempt to create a project using an epic, I get the following error: 

“There was an error syncing your Atlassian project to Jira: ASPE-19 because of an unknown error, please try again.”

Considering that the UI error message provided no context for me to troubleshoot the issue, I performed the request and reviewed the console log within the Chrome Dev Console to see if I could identify the exact error. These errors appeared in the console each time I tried to perform the action - I assume they may be related, but am not certain:

Console / Network Logs (sanitized)
- POST …/flags/api/v2/frontend/featureFlagValues → 401 Unauthorized
- @atlassiansox/feature-flag-web-client@undefined – Feature flag service returned 401, "Different client versions provided: [ClientInfo{name=feature-flag-web-client, version=undefined}; ClientInfo{name=feature-flag-web-client, version=null}]". This request will not be retried until the user data has been changed.
- GET …/gateway/api/watermelon/organization/containsAnyWorkspace?cloudId=<redacted> → 401 Unauthorized
- Warning: "Multiple versions of FeatureGateClients found on the current page. The currently bound version is 4.10.0 or earlier when module version 5.5.1 was loading."

What I’ve Tried So Far (all unsuccessful):

• Cleared browser cache and cookies, fully signed out and back in

• Disabled all extensions, tried different browsers (Chrome, Firefox), incognito mode

• Verified cross-site cookies for Atlassian domains (*.atlassian.com, *.api.atlassian.com) are allowed

• Attempted the same on different devices and networks

Questions:

1. Could this be caused by missing permissions or admin restrictions (e.g., a global "Atlas for Jira Cloud" permission)?
2. Is this a known issue involving the feature-flag or “watermelon” gateway failing due to auth/session issues?
3. Any pointers on additional diagnostic steps (like capturing x-trace-ID or headers) before escalating to official support?
4. If this is a known bug, is there a workaround (e.g. reauthenticating, feature toggle, etc.)?

Goal:

Clarify whether this behavior is expected (e.g., due to account/session/auth issues) or a platform bug. I’d appreciate any guidance.

Thanks in advance for any insight!

[Tinker Fadoua]

Hi @bradley 

Are you still having this issue? I am asking as sometimes glitches happen.

Out of curiosity did you try from a different browser? How about incognito mode?

Best,

Fadoua 

[bradley]

Hey @Tinker Fadoua

I have tried the following:

• Clearing cache/cookies
• Logging out and back in
• Disabling extensions 
• Incognito Mode
• Multiple Browsers
• Different Jira Projects and Epics
• I even went as far as trying different devices to test if my corporate device had potential blocking in place via proxy etc.

Unfortunately no luck :( 

[Tinker Fadoua]

I requested Atlassian's assistance since you tried every single step we can think of.

Best,

Fadoua

[bradley]

Hi @Tinker Fadoua , appreciate it, thank you!

[Beverley]

Hi @bradley

Thanks for providing the detailed information of the issue and all the troubleshooting steps you've tried!

Usually the Atlassian Home for Jira Cloud integration is enabled by default, but could you please check if the integration has been enabled for your cloud site and try to toggle it off/on?

Here's the link to the integration configuration page: https://{insertyoursitehere}.atlassian.net/plugins/servlet/ac/com.atlassian.atlas.jira/addon-config-page

If it's still not working, feel free to log a support ticket with our team here, and we can investigate this further: https://support.atlassian.com/contact/
Or we can create a new support ticket on your behalf.