Integrations

Reqflo integrates with the issue trackers and project tools your team already uses. The core idea is straightforward: link a ticket, issue, or work item to a journey’s Coverage panel so you can see — at a glance — which requirements and acceptance criteria are proven by that journey.

​

When to use it

Use integrations when you want to:

• Trace a journey back to the ticket or story that requested the behavior it tests.
• Show stakeholders which requirements are covered and which have gaps.
• Keep your API workflows connected to the work items driving them, without maintaining a separate mapping by hand.

​

Key concepts

Coverage is a journey-level view in Build mode. It shows which acceptance criteria are mapped to the journey and helps you identify gaps. Connecting a ticket from GitHub, Jira, or Linear to a journey’s Coverage means that ticket becomes part of the traceability picture — you can answer: does this journey prove the intended behavior? Work items / tickets are the issues, stories, or tasks from your external tools. Reqflo links to them by reference; it does not duplicate or sync their full content. Connectors are a planned step type that will let you interact with external systems during a journey run. They are distinct from the work-item integrations described here — see Connectors.

​

How it works

Each integration lets you search for and attach external work items to a journey’s Coverage panel. Linked items appear alongside your acceptance criteria, giving you a unified view of what the journey is meant to prove. Reqflo holds a reference to the item; no external data is duplicated beyond what is needed to display the link.

​

Supported integrations

​

Related pages