Integrations
IronArchitects meets your toolchain in two places: requirements flow in and out of Jira, and delivery plans flow into Jira or Azure DevOps with status syncing back. Integrations is where those connections are configured.
Plan Availability
Tool integrations are available on the Medium plan and above.
Connect a Tool
Each connection takes the tool's URL and a credential (an API token or personal access token you create in the tool with minimal scopes). Credentials are stored encrypted, shown never, and every connection can be tested before anything depends on it.
What Uses the Connections
| Feature | Connection | Direction |
|---|---|---|
| Requirements import | Jira | Read: epic stories in as drafts |
| Requirements export | Jira | Write: an epic with child stories |
| Delivery export | Jira or Azure DevOps | Write once: epics and children created |
| Delivery twin sync | Jira or Azure DevOps | Read: statuses back on a schedule |
The platform never edits or deletes items it did not just create, and never transitions work items; your tracker remains the source of truth for work.
One Service Account Beats Personal Tokens
Create the credential under a service account in your tool, not a person's login; integrations should not break when someone changes teams.