Title: Rovo app for ChatGPT returns API URLs instead of browsable Jira URLs
Description:
When using the Rovo app (Atlassian integration) in ChatGPT to query Jira issues, the app correctly finds and returns issue information. However, the links it provides are REST API URLs instead of user-facing browsable URLs.
Example:
URL returned by the app:
<a href="https://api.atlassian.com/ex/jira/15d6eba0-16bc-4e5c-9fec-239eb6681f53/rest/api/3/issue/64105" rel="noopener nofollow noreferrer" target="_blank">https://api.atlassian.com/ex/jira/x</a>xxxxxxxxxxxxxx
Expected URL:
<a href="https://unicait.atlassian.net/browse/ERPS-4985" rel="noopener nofollow noreferrer" target="_blank">https://unicait.atlassian.net/browse/ERPS-x</a>xxxxxxxxx
What happens when clicking the link:
The browser returns a JSON error:
<span>{"errorMessages":["Issue does not exist or you do not have permission to see it."],"errors":{}}</span>
This is misleading because the issue does exist and the user has full access to it — the problem is simply that the browser cannot authenticate against the REST API endpoint.
Impact:
This significantly reduces the usefulness of the integration. The natural workflow is to query issue details conversationally in ChatGPT and then click through to Jira when deeper inspection is needed. Without working links, the user has to manually copy the issue key and navigate to Jira, which defeats the purpose of the integration.
Expected behavior:
The app should return standard browsable URLs in the format https://{site}.atlassian.net/browse/{issueKey} so users can seamlessly navigate from the ChatGPT conversation to the Jira issue in their browser.
Environment:
