When to use it
- Your team tracks features and bugs in Linear and you want journeys tied to the issues that define them.
- You want to surface coverage gaps: which Linear issues are proven by a journey, and which are not yet tied to any workflow?
- You are preparing a release or milestone review and need to show which issues are exercised by your API workflow suite.
Key concepts
Coverage is a journey-level view. Linking a Linear issue connects it to the whole journey — the claim is: “this journey exercises the behavior described in this issue.” Issue reference — Reqflo stores a reference to the Linear issue (team identifier and issue number, for exampleENG-204). It does not sync comments, status, or project details 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 issues.
How it works
Open the Coverage panel
Open a journey in Build mode and select the Coverage panel from the side panel options.
Add a Linear issue
Choose Linear as the source and search for or paste the issue identifier. Reqflo resolves the issue title and displays it in the panel.
Save the link
Confirm the selection. The issue now appears under Coverage for this journey. Add multiple issues if the journey covers more than one work item.
Examples
A journey that exercises an authentication flow might be linked to the Linear issue that described it:Related pages
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.

