Post Run Evidence Back to Jira

Category: Integrations

Use evidence posting when a Reqflo journey has been executed and the result should be visible in Jira.

This workflow requires Jira write access.

Purpose

Posting run evidence back to Jira keeps planning status connected to validation results.

This workflow starts with a linked Reqflo journey, executes validation, and posts a summary of the result to the relevant Jira work item.

Use this workflow when Jira should reflect whether the linked workflow has passed, failed, or still needs attention.

Best-fit use cases

Use this workflow for:

• QA signoff
• Release readiness
• Bug verification
• Pull request validation
• Sprint completion
• Regression evidence
• Support escalation follow-up
• Incident remediation validation
• Acceptance criteria confirmation
• Customer-impacting workflow review

Inputs

This workflow starts with:

• A Reqflo journey
• Linked Jira work items
• Runnable scenarios or variants
• Configured environment
• Completed run result

Useful run fields include:

• Run status
• Journey name
• Scenario status
• Variant status
• Environment
• Timestamp
• Failed assertions
• Failed responses
• Duration
• Evidence link

Workflow steps

1. Link the journey to Jira work

Before posting evidence, the journey must be linked to one or more Jira issues.

The link determines where evidence can be posted.

2. Run the journey

Execute the journey manually, through CI, from a runbook, or from another workflow trigger.

The run should generate evidence for each relevant scenario and variant.

3. Review the run result

Review the run summary in Reqflo.

The result should show:

• Overall status
• Passed scenarios
• Failed scenarios
• Passed variants
• Failed variants
• Assertion failures
• Response failures
• Environment
• Timestamp
• Evidence link

4. Confirm the Jira update target

Select which linked Jira item should receive the update.

A journey may be linked to multiple Jira items, so evidence should be posted to the work item or items it directly supports.

5. Click "Post result to Jira"

Reqflo posts a comment or status update to Jira.

The Jira update should summarize the validation result without requiring the reader to leave Jira for basic context.

6. Review the Jira comment

The Jira comment should include:

• Reqflo validation status
• Journey name
• Environment
• Completion status
• Passed and failed scenario count
• Failed scenario or variant, if any
• Failure summary, if any
• Link to full Reqflo run evidence
• Timestamp

Output

At the end of this workflow, Jira should contain a validation summary from Reqflo.

Reqflo should also track:

• Evidence posted status
• Jira issue updated
• Posted timestamp
• Posted result
• Link between Jira comment and Reqflo run, if available

Example Jira comment

Reqflo validation result: Failed

Journey: Tenant onboarding
Environment: Staging
Completion: 7 of 9 scenarios passing
Failed scenario: Invite user to tenant
Failed variant: Non-admin user attempts invite

Failure summary:
Expected 403 Forbidden, received 200 OK.

Full run evidence:
[Link to Reqflo run]

SDLC value

Posting evidence back to Jira closes the loop between planning and validation.

Jira remains the system of record for work tracking, while Reqflo remains the system of record for workflow validation.

This improves:

• Release communication
• QA signoff
• Bug verification
• Auditability
• Cross-functional visibility
• Engineering handoff
• Support follow-up
• Stakeholder confidence

Teams can see whether work is complete, what evidence supports it, and what still needs attention.

Recommended completion states