Custom Rovo Agent No Longer Respects Dynamic Context Selection in Chat Interface

[Ranvijay Singh]

Here's a concise version:

---

Product: Rovo Studio and Rovo Chat — Custom Agents
Severity: High
Organization: Under Armour

Issue

Custom Rovo Agents created in Studio no longer pick up the dynamic context (Confluence space, Jira project/board) selected by the user in the Chat interface. Agents now only reference the static Knowledge sources configured during agent creation, ignoring the chat context selector entirely.

Previous Behavior: Users could select a Confluence space or Jira board in the chat context selector, and the custom agent would use that context alongside its configured Knowledge sources. This allowed a single agent to serve multiple project teams seamlessly.

Current Behavior: The agent ignores the chat context selector and only queries its statically configured Knowledge sources.

Steps to Reproduce

1. Create a custom agent in Studio with Knowledge scoped to Space A

2. Open Rovo Chat, invoke the agent, and select Space B in the context selector

3. Ask a question requiring information from Space B

4. Agent only searches Space A — Space B is ignored

Business Impact

• Agent duplication — Without dynamic context, we must create separate copies of the same agent for every project team, making management unsustainable at scale

• Poor UX — Users must locate the correct project-specific agent from a growing list instead of simply switching context in one unified agent

• Maintenance burden — Any update to instructions or prompts must be replicated across all duplicates individually

• POC blocked — Our active Rovo Agent POC (Estimation Buddy, Story Readiness) relies on agents working across multiple sprint boards and projects dynamically

Expected Resolution

1. Restore dynamic context — Custom agents should respect the space/project/board selected in the chat context selector

2. Provide a toggle — If the change was intentional, add a Studio option (e.g., "Allow dynamic context from chat") so agent creators can choose the behavior

3. Communicate the change — Publish documentation explaining the rationale and migration path

[Trudy Claspill]

Hello @Ranvijay Singh 

Be advised that this is a user community. We are mostly not Atlassian Team Members. We don't have the ability to change the app. We can only offer you advice on how to address your concern.

In this case if you want to get feedback directly to Atlassian you need to either open a support case with Atlassian Technical Support or use the Feedback option within the app under the Help button.

Your post tags indicate you are using a Free subscription. Customers on Free subscriptions do not have access to open cases directly with Atlassian Technical Support. That leaves you with the Feedback option available in the app itself.