Customers using Rovo Chat for complex, multi-step Jira workflows (e.g., identifying duplicates and performing bulk transitions across multiple statuses) have reported inconsistencies in how the system validates and reports task completion.

Key Requirements:

1. Accurate Completion Reporting: Ensure Rovo only reports a step as "completed" if the underlying Jira action (e.g., transition) has been successfully validated by the API. Currently, Rovo may report success even if the transition was not applied.

1. Clear Error Handling: When a task cannot be reliably executed (due to complexity, missing required fields, or multi-step limitations), Rovo should clearly indicate the failure and the specific reason (e.g., "Transition requires a Resolution field which is not currently supported in bulk").

1. Proactive Guidance: Provide alternative approaches or suggestions (such as using a custom Rovo Agent) when the general Rovo Chat encounters a workflow it cannot consistently handle.

1. Validation Before Confirmation: Avoid prompting for user confirmation or showing "Step completed" UI elements unless the backend action has been verified.