Since approximately 29 July 2026, Rovo has stopped correctly using the context of the currently opened Jira issue from which the chat is launched.
The issue was working correctly before that date and no changes were made by the user to prompts, projects, or workflows.
The problem occurs across multiple Jira projects.
When Rovo chat is launched from a Jira issue and the issue appears in the Context section of the chat panel, Rovo should be able to:
- identify the currently opened issue
- read its title
- access its description and fields
- answer questions based on the displayed context
Example:
User message:
What issue is this chat currently running from?
Expected response:
AR-1485- "Rozdzielenie widoku "
Actual behavior
Although the Context section correctly shows the currently opened issue, Rovo does not use that context.
Different incorrect behaviors can be observed:
Scenario 1 - Hallucinated issue
Current issue:
AR-1485
Context chip:
AR-1485
Rovo response:
SUPPORT-12345 - Error during monthly report generation
The issue does not exist and is unrelated to the currently opened issue.
Scenario 2 - Asking for issue key
Current issue:
AR-1485
User asks:
Which issue am I currently viewing?
Rovo response:
I need the issue key or project name.
The issue key is already available in the displayed context.
Scenario 3 - Using conversation memory instead of page context
Current issue:
AR-1485
Context chip:
AR-1485
User asks:
Do you recognize the context of the issue from which this chat was launched?
Rovo responds with details of a completely different issue:
APBS-1827
This appears to come from conversation history rather than the currently opened Jira issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.