This is what I'm currently getting when trying to use the Atlassian Rovo connector in GPT Chat. Is this normal, or do I need to do something to make it work? Until December 16, 2025, this worked without any configuration. Simply connecting Atlassian Rovo to GPT Chat allowed GPT to interact with JIRA.
Short version:
At the moment, the Atlassian Rovo connector does not provide live access to Jira data from this ChatGPT integration, despite being listed as connected.
What happens in practice:
The Rovo connector is visible and advertised with capabilities such as File Search and Writes.
However, any attempt to access real Atlassian resources (for example, calling methods like getAccessibleAtlassianResources or querying Jira projects/issues) fails.
The connector consistently returns errors such as 404 – “Link not found”.
Because of this:
Jira projects are not discoverable
Boards are not accessible
JQL queries cannot be executed
Jira issues cannot be read or analyzed
Resulting limitation:
Even though the connector appears enabled in the Atlassian UI, the underlying MCP/Rovo backend does not expose Jira context to ChatGPT at runtime. From the integration’s perspective, Jira is effectively unavailable.
Important clarification:
This is not a permission or configuration issue on the project side. The failure occurs at the connector / MCP layer before any project-level access checks are possible.
Expected behavior (for comparison):
Ability to resolve accessible Atlassian Cloud resources
Ability to read Jira projects and execute JQL queries
Ability to analyze boards and issues via Rovo
Actual behavior:
Connector initializes
Resource discovery fails
Jira API surface is unreachable
Conclusion:
At the moment, the Atlassian Rovo connector in ChatGPT operates in a limited or degraded mode and cannot be used for Jira analysis or automation, despite being listed as available.
.
Got it, thanks! If I understand correctly, will it be possible to work with Jira through Atlassian Rovo in ChatGPT in the near future, as was previously the case? Or is this a natural limitation, and is Atlassian currently maintaining its policy of restricting Atlassian Rovo from working in ChatGPT indefinitely?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Vladislav Popov ,
The previous was may not be fully accurate, I is not deeply involved in this integration, but as i said earlier there have been some changes in Atlassian Cloud around mid-December that might help address this. I have listed the relevant updates specifically related to Rovo, which you can refer to in the attached document.
https://confluence.atlassian.com/cloud/blog/2025/12/atlassian-cloud-changes-dec-8-to-dec-15-2025?
If you do not find the required information in these changes, you may raise a ticket with the Atlassian Support team for better clarity and understanding.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.