Skip to main content
Connect Reqflo to Jira to attach tickets to journey Coverage. Once linked, a Jira issue appears alongside the journey’s acceptance criteria, giving you a clear line between the ticket that described the requirement and the journey that exercises it.

​
When to use it

  • Your team uses Jira for stories, epics, or bug reports and you want journeys traceable back to the tickets that motivated them.
  • You want to show which Jira tickets are covered by your API workflow suite — useful for sprint reviews, release sign-off, or audits.
  • You need a lightweight way to answer “which journey proves this ticket?” without leaving Reqflo.

​
Key concepts

Coverage is a journey-level view. Linking a Jira ticket connects it to the whole journey, not to individual steps. The claim is: “this journey exercises the behavior described in this ticket.” Ticket reference — Reqflo stores the Jira project key and issue number (for example, PAY-142). It does not sync comments, status, or fields beyond what is needed to display the link. Build mode is where you manage coverage. Open a journey, switch to Build, and use the Coverage panel to add or remove linked tickets.

​
How it works

1

Open the Coverage panel

Open a journey in Build mode and select the Coverage panel from the side panel options.
2

Add a Jira ticket

Choose Jira as the source and search for or paste the issue key. Reqflo resolves the ticket summary and displays it in the panel.
3

Save the link

Confirm the selection. The ticket now appears under Coverage for this journey. You can link multiple tickets if the journey covers more than one item.
4

Review coverage

Use the Coverage panel to check which tickets are tied to this journey and identify any criteria that are not yet covered.

​
Examples

A journey that exercises a refund flow might be linked to the Jira story that defined it: 
Project: PAY
Issue:   PAY-317 — Refund: partial refund must not exceed original charge
Journeys that span multiple acceptance criteria can reference several tickets: 
Project: PAY
Issues:  PAY-317, PAY-318, PAY-401
These references appear in the journey’s Coverage panel alongside any other acceptance criteria you’ve added.

Coverage panel

Manage all coverage links for a journey in Build mode.

Coverage concept

What coverage means in Reqflo and how to think about gaps.

Integrations overview

All supported integrations.

Build mode

The journey canvas where you configure steps and coverage.