Rovo Chat returns 401 Unauthorised when querying Jira Assets

Summary

When using Rovo Chat to query Jira Assets schema data, the agent may return an HTTP 401 Unauthorized error or fail to find results, even if the user has Org Admin, Jira Admin, and specific Assets Schema permissions.

Diagnosis

Rovo Chat fails to return Assets data and instead shows errors (e.g., 401 Unauthorised) in the chat interface or browser console.

Cause

Rovo's reasoning engine may incorrectly route the request to a different skill (such as the Confluence skill) instead of the Assets skill. When a non-Assets skill attempts to access the Assets API, it lacks the necessary credentials/context, resulting in a 401 error.

• Verification: Check if the prompt is being interpreted as a general search or a Confluence search rather than an Assets query.

Solution

1. Use Explicit Commands (Immediate Workaround)

To bypass Rovo's intent reasoning and force the use of the correct skill, prepend your prompt with the explicit Assets command:

• Command: /search-assets

• Example: /search-assets show me a list of "name" attributes for the "Hardware" schema.

2. Refine the Prompt

If you prefer not to use explicit commands, make the prompt more specific to help Rovo's intent model map the request to Assets:

• Avoid ambiguous terms that might trigger a Confluence or general Jira search.

• Clearly state the Schema Name and Object Type.

3. Use a Custom Rovo Agent

Create a custom Rovo Agent in Rovo Studio and explicitly add the Jira Assets skill to that agent. This ensures the agent always has access to the Assets toolset without relying on the general chat's routing logic.