Issue Summary

In our current Jira integration, the intermediate results lack both the Story Points and the Team custom field. They only include basic fields such as key, summary, status, assignee, and URL. As these fields are not available in the data received by the assistant, it cannot conduct the requested group-by analysis, such as issue count by Story Points or Story Points by Team. This limitation persists even though Jira's UI can display and group by these fields and throws an internal error during its execution.

Steps to Reproduce

1. In Jira Cloud, open Rovo Chat.
2. Prompt Rovo to summarize a recently closed Sprint, grouped by Team and Story points.
3. Observe that no data is returned.
4. Click the generated JQL smart link—Jira Search shows no results.
5. Note it's counting 0

Expected Results

Rovo should reflect the Jira  JQL count on the smart link, and if there is something not supported, it should be friendly disclaimed to the user. 
 

Actual Results

The Smart links can't understand the query and return 0 Items

The below exception is thrown in the log file:

• Splunk logs show:

• • All events with logger_name: io.atlassian.micros.convoai.agent.minions.toolminions.jirabatchagents.JqlExecutionSchemaAgent and ctx_executable_agent_name: JiraTool return "firstBatch returned 0 jira issues".

• • Exception in logs:

    io.atlassian.micros.convoai.platform.client.jira.JiraRestClientException: Failed to search Jira fields: 500 Internal Server Error from POST http://jira-monolith-archetype.mesh:20039/rest/api/3/field/search

     

Workaround

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