Issue Summary

When a user sends a prompt to Rovo Chat that involves creating or configuring Jira issues without explicitly specifying an issue type (e.g., Bug, Story, Task), the backend attempts to call an internal tool that requires the issue type as a mandatory parameter. Because the issue type is not provided, the call fails with an exception and triggers a lengthy recovery path, resulting in response times of approximately 60 seconds instead of the expected 10–15 seconds.

Steps to Reproduce

1. Open Rovo Chat on any Atlassian Cloud site with Jira connected.

1. Send a prompt that references Jira issue creation or configuration without specifying an issue type — for example: "I want to create an automation for when a user in a specific group creates an issue, then the team field should match that group."

1. Wait for the response.

Expected Results

Rovo Chat should respond within 10–15 seconds. If the issue type is not specified in the prompt, the system should automatically resolve available issue types before proceeding, without throwing an internal error.

Actual Results

Rovo Chat takes approximately 60 seconds to respond. The backend fails to resolve the required issue type parameter, throws an internal exception, and enters a recovery path that adds ~30 seconds of additional processing time before delivering the final response.

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available