Rovo Agents in Slack fail to search JSM with permission errors

Summary

Custom Rovo agents used within Slack channel threads may return a permission error (e.g., "I don't have permission to search JSM") and fail to retrieve results from Jira Service Management (JSM). This occurs even when the same agents function correctly in Rovo Studio or in general Jira spaces.

Diagnosis

Slack logs may indicate a warning such as [AGENT_TOKEN] No agent-specific bot token found... falling back to master app token, which can lead to permission failures when the agent attempts to access specific project data via the Slack integration.

Cause

The issue is typically caused by a lack of explicit agent-specific authorization within the target JSM project or space.

Solution

To resolve this, ensure the Rovo agent is explicitly added to the relevant JSM project or space:

1. Navigate to the Jira Service Management project where the search is failing.

2. Go to Project Settings > Rovo.

3. Add the Rovo for Slack agent (or the specific custom agent) directly to the project's agent list.

4. Verify that the agent now has the necessary permissions to search and retrieve content within that space via slack.