Summary

When using a Rovo Agent to break down a source document (PDF, Doc, image, etc.) into a Jira work hierarchy, the agent successfully extracts the data, displays the proposed breakdown of Epics, Stories, and Tasks/Sub-tasks, and creates Epics and Stories — but fails to create Tasks/Sub-tasks on the first attempt. The user must then manually reinforce the request to create the missing sub-tasks, which then succeeds without issue.

This happens because Jira's bulk issue creation API does not support creating sub-tasks in the same operation as their parent Stories. Since the parent Stories don't yet have issue keys at the time the sub-tasks are submitted, the creation silently fails. The agent does not currently handle this by sequencing the creation into multiple API calls.

Expected behavior: The user provides a source document, the agent proposes the hierarchy, and upon confirmation, creates all Epics, Stories, and Tasks/Sub-tasks end-to-end without requiring additional prompts.

Current behavior: Epics and Stories are created, but Tasks/Sub-tasks are silently dropped, requiring the user to notice the gap and re-request creation.

Suggestion

The Rovo Agent should implement sequential, dependency-aware issue creation so that the full hierarchy is created in one user-initiated attempt.