Rovo Jira connection unable to retrieve issue and comment details

[Malini Sivanantham]

Question:
Why is Rovo no longer able to access Jira issue and comment content? The user session is active and valid, so is this related to a recent connector or Jira integration change?

Rovo was previously able to access Jira tickets, comments, and related content. It is now unable to retrieve the details for Jira issue ONE-112045 – U of Georgia PROD - PV header fails to render on initial page load.

When attempting to audit the test cases, Rovo returned the following errors:

• “The Jira retrieval service returned an access error in this session.”
• “I am unable to automatically fetch content directly from your Jira comment link (ONE-112045 / Comment 1166362) due to an environment access limitation.”
• The backend connector service returned an unexpected internal error: HTTP 400 Bad Request.

Rovo also indicated that authentication is not required because the user session is active and valid. This appears to be a temporary connector or service issue rather than a user authentication or permissions problem.

Expected behavior:
Rovo should be able to retrieve and read the Jira issue, comments, test cases, expected results, screenshots, and fix summary directly from Jira. It should also be able to perform the requested audit and update Jira content when the user has the appropriate permissions.

Actual behavior:
Rovo cannot read the Jira issue or comment content and instead requests that the user manually copy and paste the test cases and screenshots into the chat.

Impact:
This prevents Rovo from:

• Reading Jira issue details and comments
• Reviewing test cases directly from Jira
• Auditing expected results and screenshots
• Identifying redundant or missing test coverage
• Updating Jira comments or issue content live

Troubleshooting already performed:

• Confirmed that the user session is active and valid.
• Confirmed that the issue and comment link are valid.
• The failure occurs when retrieving both the Jira issue and comment content.
• The error returned is HTTP 400 Bad Request from the backend connector service.

Request:
Please investigate whether there has been a recent change to the Jira/Rovo connector, permissions, API behavior, or environment configuration. Please restore Rovo’s ability to read Jira issue and comment content and perform live Jira updates where permitted.