-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Medium
-
Component/s: Rovo Slack app
-
None
-
Severity 3 - Minor
Issue Summary
When using the integration Rovo + Slack and asking Rovo chat to create a Jira Work Item, Rovo receives errors.
Steps to Reproduce
- Integrate Rovo with Slack
- Add a Rovo Agent in Slack
- Make sure that the Agent has the correct skills to create a Jira Work Item
- Make sure the Agent has permission to access the Jira instance and to create work items
- In Slack, open a Rovo Chat
- In the Chat request to Rovo, create a new Jira Work Item, like a Epic
- Make sure to send the mandatory fields to create it according to the Jira Work Item configuration
Expected Results
The Jira Work Item is created without issue.
Actual Results
The Rovo Chat returns errors. The error message can be:
"Invoked action Jirasmartissuecreatetool is not supported yet. "
In the logs, we can see:
{
cloudId: XXXXXXX-YYYYYYY-ZZZZZZZ
ec2: {
}
env: prod-east
eventId: Ev0XXXXXXXX
level: INFO
logger_name: com.atlassian.rovoslacksvc.infrastructure.events.processor.SlackEventProcessor
m: {
}
message: Unsupported action detected JiraSmartIssueCreateTool. Skipping action input blocks.
micros_container: microservice
slackRequestId: XXXXXX-YYYYYYYYY-ZZZZZZZZ
thread_name: luiztest-http-epoll-1
time: 2026-03-19T20:49:43.942135396Z
Or can be:
"There was an error creating the Jira issue, either due to a missing required field or an internal error. Please review your input and try again."
Which in logs contains:
{
cloudId: XXXXXXXXXXXXXXXXXXXXXX
ec2: {
}
env: prod-east
level: INFO
logger_name: com.atlassian.rovoslacksvc.domain.actions.mapper.BaseActionDataMapper
m: {
}
message: Running mapToExecutionRequest with key: jira-atlassian-work-item-create-all-field-types, XXXXXXXX
micros_container: microservice
spanId: XXXXXXXXXXXXXX
thread_name: tomcat-handler-XXXXX
time: 2026-03-25T15:40:24.255312376Z
traceId: XXXXXXXXXX
traceSampled: false
}
{ [
cloudId: XXXXXXXXXXXXX
ec2: {
}
env: prod-east
level: INFO
logger_name: com.atlassian.rovoslacksvc.domain.actions.mapper.JiraWorkItemCreateAllFieldTypesMapper
m: {
}
message: projectKey not present in original data and not updated, skipping enrichment
micros_container: microservice
spanId: XXXXXXXXXXXX
thread_name: tomcat-handler-XXXXX
time: 2026-03-25T15:40:24.255314776Z
traceId: XXXXXXXXXXXXXX
traceSampled: false
}
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available