IntegrationsJira
Recommended in-app surfaces
Recommended Jira integration surfaces for import, journey validation, and scenario coverage.
Recommended In-App Surfaces
Category: Integrations
The Jira integration should feel like a workflow validation system, not a generic issue sync.
Jira import page
The Jira import page should function as a planning and coverage control panel, not just a bulk importer.
It should show:
- Connected Jira workspace
- Available Jira projects
- Search and filters
- Importable issues
- Already-linked issues
- Journey each issue is linked to
- Coverage status
- Latest run status
- Evidence status
- Suggested action
Recommended issue labels:
| Label | Meaning |
|---|---|
| Not linked | Jira issue is not connected to a Reqflo journey |
| Linked to journey | Jira issue is already connected |
| Coverage missing | No scenarios are mapped yet |
| Partially covered | Some scenarios or variants are mapped |
| Covered | Required scenarios or variants are mapped |
| Evidence missing | No run evidence exists |
| Evidence available | At least one run supports this item |
| Evidence stale | Existing evidence is older than the freshness threshold |
| Latest run passed | Most recent run passed |
| Latest run failed | Most recent run failed |
Journey page
The journey page should act as the validation source of truth.
It should show:
- Linked Jira work items
- Work item coverage
- Scenario mapping status
- Variant mapping status
- Latest run result
- Completion rate
- Evidence links
- Last posted Jira status
- Open gaps
- Readiness status
Example:
Linked Jira work
REQFLO-8 - Tenant onboarding API
Coverage: 4 of 5 scenarios mapped
Latest run: Passed
Evidence: Available
REQFLO-7 - Billing setup step
Coverage: 2 of 4 scenarios mapped
Latest run: Failed
Evidence: Available
REQFLO-6 - Invite flow permissions
Coverage: 1 of 3 scenarios mapped
Latest run: Not run
Evidence: MissingScenario card
Each scenario card should show the operational status of that behavior.
It should include:
- Scenario name
- Linked Jira issue
- Variants
- Request templates or endpoints used
- Mapping status
- Latest run status
- Evidence link
- Missing mappings
- Blocking failures
Example:
Scenario: Admin invites user to tenant
Linked work item: REQFLO-6
Variants:
- Admin invites valid user - Passing
- Non-admin attempts invite - Failing
- Existing user is invited again - Not mapped
Coverage: 2 of 3 variants mapped
Latest run: Failed
Evidence: Available
Blocking gap: Existing user variant is not mappedProduct positioning
Core positioning:
Plan work in Jira. Prove it in Reqflo. Keep the evidence connected.Expanded positioning:
Reqflo connects Jira planning to executable API workflow evidence. Teams can import or link Jira work, generate workflow scenarios, map those scenarios to real requests, track coverage, and post validation results back to Jira when work is ready.Product value:
Reqflo helps teams prove that planned API work actually works.