Delivery integrations
Delivery Integration Center
Push approved requirements and full project context directly into Jira and Confluence — the tools your delivery team already works in. No copy-paste, no manually re-typing what RequirementsHub already has structured.
Jira
Connect once per workspace through the same Atlassian sign-in Confluence uses. Pick your target Jira Space, then configure field mapping: Title and Description map automatically (Summary and Description — not configurable); Priority and Requirement Type are yours to set, pre-filled with sensible BABOK-aligned defaults you can override; Acceptance Criteria maps to a Jira custom field — RequirementsHub auto-suggests one if your Space has a field named “Acceptance Criteria” or “AC,” or you can pick manually. No matching field? Create one in Jira, or opt into folding Acceptance Criteria into the Description field (available, not recommended — it combines two different things into one).
A requirement won’t push until its mapping actually resolves: every Requirement Type needs a mapped Jira work type (or a default), and the requirement itself needs to be approved. If something’s not ready, RequirementsHub tells you exactly why — not a silent failure.
Confluence
Connect the same way — one Atlassian sign-in, a Confluence Cloud account with Add/Edit permission on your target Space. Workspace owners set a default Space and, optionally, a default parent page; everything published nests underneath it.
Publish a single requirement or artifact from its detail page, or publish an entire project as a linked page tree — a project overview (objectives, stakeholders, constraints, systems), a requirements index, and one dedicated page per requirement with its description, acceptance criteria, type/priority/status, and full traceability back to its ID and parent. Re-publishing updates the existing page in place — versioned, never duplicated — and RequirementsHub tracks whether your RequirementsHub content has changed since the last push, so you always know if Confluence has drifted.
FAQ
- Does RequirementsHub ever push without my say-so?
- No — every push is a deliberate action, single item or full project, never automatic.
- Who can change the default Jira Space or Confluence Space?
- Workspace owners only. These are separate settings — connecting Jira doesn’t affect your Confluence Space, and vice versa.
- What stops an unready requirement from reaching Jira?
- Unapproved requirements, unmapped types, or unresolved required fields all block the push with a specific reason shown.
Connecting an AI assistant to your account instead? See connecting an AI assistant. Running intelligence locally? See Resident MCP.