Why ROVO Agents are picking the wrong context when we are using two boards with different teams

[Ranvijay Singh]

Hi ROVO Team,

I am noticing multiple issues following the recent rollout mentioned as “ROVO agents are moving to an improved model from April 14, 2026.”

In my sandbox setup, I have a Jira project configured with two different boards. I am using a custom ROVO agent that I defined and explicitly referencing the intended project and board context while interacting with the agent.

While the agent initially returns results, the behavior becomes inconsistent when I open a second window or browser tab. For the new board, the agent continues to return results from the previously referenced board, making the experience confusing. This was not the behavior earlier.

Additionally:

• When I change the board within the Jira space, the ROVO context does not update accordingly.
• The ROVO side panel does not refresh to reflect the newly selected board.
• As a result, the agent keeps operating on the older board context, even though a different board is actively selected.

It appears that the new model has impacted some of the context‑switching and context‑persistence capabilities that were working correctly earlier, particularly in multi-board and multi-tab scenarios.

Requesting your support to review this regression and advise on whether this is a known issue with the new rollout or requires a configuration/workaround on our side.

Thanks,
Ranvijay

[Rebekka Heilmann _viadee_]

Hi @Ranvijay Singh 

with a revent Rollout, opening Chat in a new Tab will open the already existing Chat from the other Tab. So you should see the Chat history.

What should update is the current context that you see above the text field in Chat. But: If you continue using the same Chat, it may also still refer to the old board as that is part of the Chat history and Rovo Chat has started to use its "memory" more often now.

To get clear results, it's best to open a fresh Chat by clicking the Edit Button at the top menu in Chat.

There was a problem with selecting the correct context for Chat that other users have reported so maybe that was mixed in with your problem as well. Should be resolved now.