Skip to content

Jira and Azure DevOps Export

The delivery plan becomes real when it lands in the tracker your teams already use. IronArchitects exports to Jira and Azure DevOps, then keeps a live picture by syncing status back: the delivery twin.

Before You Start

Connect Jira or Azure DevOps in Settings → Integrations (Medium plan and above), and have a generated delivery plan on an approved package.

Export

  1. On Operate → Delivery, choose Export and pick the connection and target project.
  2. The export creates epics first, then their children in batches, preserving the plan's ordering and parent links.
  3. Every exported item stores its external key, and the panel links each item straight to the created issue.

The export is resumable by design: if it is interrupted, run it again; items already created are skipped, never duplicated. If the tracker rejects an individual item, the error is shown on that item and the rest of the export completes; fix and re-export to pick up the stragglers.

The Delivery Twin

After export, status flows back automatically on a schedule (and on demand with Sync Now): items move through planned, exported, in progress, and done based on their status in your tracker.

  • Per-phase progress bars and the per-component badges on the canvas update from the sync.
  • An issue deleted or unrecognized in the tracker is counted as missing; it never silently flips an item's status backward.
  • Execution feeds drift detection: building out of sequence, skipping security tasks, or marking work done that is not observed in the environment each raise findings.

The Tracker Stays the Source of Truth for Work

IronArchitects never edits, transitions, or deletes issues after creating them. Teams work entirely in Jira or Azure DevOps; the platform only reads status back.