Why Rovo app for ChatGPT returns API URLs instead of browsable Jira URLs?

[AZamorano]

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:
  https://api.atlassian.com/ex/jira/xxxxxxxxxxxxxxx

• Expected URL:
  https://unicait.atlassian.net/browse/ERPS-xxxxxxxxxx

What happens when clicking the link:

The browser returns a JSON error:

{"errorMessages":["Issue does not exist or you do not have permission to see it."],"errors":{}}

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:

• Platform: ChatGPT (OpenAI) with Rovo app installed

• Jira instance: Jira Cloud

• Browser: Any

[Tomislav Tobijas]

Hi @AZamorano ,

Can you maybe share the prompt you've been using? 

For example, when I asked Atlassian Rovo connector this:

Atlassian Rovo can you find me work items from SBOXAPP Jira project/space and list 5 key Epics?

I did get the following response:

Where all links are using the URL format from your expected result 👀

Can you maybe try reconnecting/authorizing the connector and see how it will behave then?
Alternatively, you can reach out to Atlassian Support to see if maybe they have some additional insights.

Cheers,
Tobi

[Arkadiusz Wroblewski]

Hello and Welcome to Atlassian Community @AZamorano 

test with one very explicit prompt, for example:

Find ERPS-123 and return the clickable Jira browser URL in /browse/KEY format, not the REST API URL.

Little Provocative to ChatGPT, but it can work.

Best,

Arek🤠