Skip to main content
Connect Reqflo to GitHub to attach GitHub issues to journey Coverage. Once linked, an issue appears alongside the journey’s acceptance criteria, giving you a traceable record of what the journey is meant to prove and why it exists.

​
When to use it

  • Your team tracks features, bugs, or requirements as GitHub issues and you want journeys tied to the work items that motivated them.
  • You want to answer “which issue does this journey cover?” without maintaining a separate spreadsheet.
  • You are building evidence for a release and need to show which tickets are exercised by your API workflows.

​
Key concepts

Coverage is a journey-level view, not a step-level one. When you link a GitHub issue, you are connecting it to the whole journey — the claim being made is “this journey exercises the behavior described in this issue.” Issue reference — Reqflo stores a reference to the GitHub issue (repository + issue number). It does not sync comments, labels, or assignees; the link is a pointer, not a mirror. Build mode is where you manage coverage. Open a journey, switch to Build, and use the Coverage panel to add or remove linked items.

​
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 GitHub issue

Choose GitHub as the source and search for or paste the issue reference. Reqflo resolves the issue title and displays it in the panel.
3

Save the link

Confirm the selection. The issue now appears under Coverage for this journey. You can add multiple issues if the journey covers more than one work item.
4

Review coverage

The Coverage panel shows all linked items together. Use this view to check for gaps — criteria or tickets that aren’t yet tied to any journey.

​
Examples

A payment journey that exercises a checkout flow might be linked to the GitHub issue that described the checkout acceptance criteria: 
Repository: acme-corp/payments
Issue:      #142 — Checkout: validate card expiry before charge
A single journey can reference more than one issue if it exercises multiple related requirements: 
Repository: acme-corp/payments
Issues:     #142, #155, #201
These links live in the journey’s Coverage panel and are visible to anyone with access to the journey.

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.