Hello Atlassian Support,
We are experiencing an issue where non-admin users without a Confluence license receive the following error when opening a jira:fullPage Forge module:
main.7ab801f603ece6b…01f603ece6b5b1fa:46 Error: GraphQL error: javax.ws.rs.WebApplicationException: com.atlassian.sal.api.net.ResponseException: 403 Forbidden, current user not permitted to use Confluence.
at main.7ab801f603ece6b…ce6b5b1fa:142:79680
at main.7ab801f603ece6b…ce6b5b1fa:142:74453
at Generator. (main.7ab801f603ece6b…ce6b5b1fa:142:77195)
at Generator.next (main.7ab801f603ece6b…ce6b5b1fa:142:78046)
at Zn (main.7ab801f603ece6b…ce6b5b1fa:142:78262)
at a (main.7ab801f603ece6b…ce6b5b1fa:142:80571)
This appears to be a variant of ECO-1319, where the Forge platform incorrectly fires a Confluence GraphQL query during jira:fullPage initialization. The difference in our case is that Confluence is installed on the site, but the affected users hold a Jira license only with no Confluence license. Admin users with Confluence access are unaffected.
We understand ECO-1319 was marked as fixed in Forge platform v3.22.1.
Could you please clarify:
- Has this fix been fully rolled out across all Atlassian Cloud sites, including the 403 variant described above?
- How can we verify whether a specific site has received the fix?
Reference: https://jira.atlassian.com/browse/ECO-1319
Thank you.