Issue Summary

When a user asks Rovo Chat to transition a Jira issue status (e.g., "Move PROJ-123 to In Progress"), the jira-issue-transition-bulk action is invoked for some users and fails with the error:

"Transition Jira Issues Status failed because 'transition' identified must be in integer"

Steps to Reproduce

1. Open Rovo Chat
2. Ask: "Move [ISSUE-KEY] to In Progress"
3. Observe the error message returned

Expected Results

Rovo Chat should resolve the transition name (e.g., "In Progress") to its corresponding integer transition ID by calling GET /rest/api/3/issue/{key}/transitions, then perform the transition successfully.

Actual Results

• The action jira-atlassian-work-item-update-all-field-types-bulk handles the same request successfully for other users — only users routed to jira-issue-transition-bulk are affected.
• The message_metadata for the failing call shows: "key": "jira-issue-transition-bulk", "action_execution_result": "FAILURE"

Workaround

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