Use Vansah’s test result fields in a Jira workflow rule to check testing progress before a work item moves to another status. For example, you can require an approved test status before allowing the transition to Done.
There are two parts to the setup: enable and map the Vansah fields, then configure the transition rule in Jira. Enabling the fields alone does not block any transition.
Before you begin
Ask a Jira administrator to configure the Vansah fields and the relevant Jira workflow.
Workflow validator support requires Vansah’s Advanced features to be available for your workspace.
Decide which result allows the transition, how to handle N/A results and work items with no linked tests, and whether child work item results should be included.
1. Enable the Vansah fields
In Jira’s top menu, open Apps → Vansah.
Select Configure.
Find Workflow validator and turn on Enable Vansah Custom Fields. Confirm field creation if prompted.
Check the mapped fields. The default names are shown below. Expand a field to map it to a compatible existing Jira custom field when needed, then confirm the change.
Vansah value | Default Jira field | Use |
Test Result Status | Vansah TR Status | Overall testing status for the work item. |
Pass rate | Vansah Pass Rate | Percentage used to track passing test results. |
Fail rate | Vansah Fail Rate | Percentage used to track failing test results. |
Coverage | Vansah Coverage | Percentage of the associated tests that have been executed. |
The status maps to a single-select field. The three percentage values map to number fields. If you use an existing field or rename a field in Jira, select that same field when configuring the workflow rule.
2. Check field availability in Jira
Open the mapped Jira field from the Vansah configuration.
Check that its Jira context includes the intended Jira space and work item types. Add the field to the appropriate screens or layout so users can see the value.
For the status field, check that its options include the result names your workspace uses.
Jira’s field configuration screens may look different from this example. A field’s context controls where it applies; its screen or layout placement controls where users see it.
3. Link and execute the relevant tests
Link the Test Cases to the Jira work item and execute the tests in the intended context. Check the work item’s actual Jira field value after the results are saved.
Vansah updates configured Jira fields as testing summaries are refreshed. A workflow validator checks the value stored in Jira. Verify that value before relying on it as a release gate.
4. Configure the Jira transition rule
Edit the Jira workflow used by the intended work item type and select the transition you want to control.
Add a field validation rule for the mapped status field. In the newer workflow editor, look under Validate details → Validate a field. Older editors use Validators → Regular Expression Check.
For a default passing-status check, require an exact match to
Passed. Where the rule asks for a regular expression, use^Passed$so it does not also matchPassed-In-Progress. Use your configured result label if it has been renamed.Save the rule and publish the workflow update.
Verify the rule with representative work items before your team depends on it.
For editor navigation and rule setup, see Atlassian’s workflow editor guide and workflow rule instructions.
Important: Passed is an overall result. It can include tests marked N/A, so it does not prove that every linked test individually passed. Choose the rule that matches your team’s policy.
Example of a transition blocked because the stored status is Failed.
Understand the status values
These are the default status names for directly associated tests. Customized result names may appear in your Jira field. Parent summaries can also include child work items when that option is enabled.
Status | Meaning |
No-Test-Cases | No associated Test Cases are included in the summary. |
Untested | Tests are associated, but the overall result is still untested. |
Passed | All included tests are executed, with at least one pass and no failed results. N/A results can also be included. |
Failed | All included tests are executed and at least one has failed. It does not mean every test failed. |
N/A | The completed summary contains N/A results and no passed or failed results. |
Blocked | The incomplete summary contains a blocked result. |
Passed-In-Progress | The summary is incomplete and contains passing or passed-in-progress results, without a higher-priority failing result. |
Failed-In-Progress | The summary is incomplete and contains failed or failed-in-progress results. |
N/A-In-Progress | The summary is incomplete and contains N/A or N/A-in-progress results, without a higher-priority passed or failed result. |
Include child work item results when needed
In the same Vansah configuration, Enable Child Work item Test Result Status allows parent field values to reflect child work item summaries. Enable it only when your workflow should consider child testing, and verify the resulting parent values before applying a gate.
Vansah Work View can also affect the testing scope for hierarchical work items. Check the summary and stored field for the actual parent work item; do not assume every parent uses only directly linked cases.
Verify and troubleshoot the rule
Check a work item that should pass and one that should be blocked. Include untested, N/A, no-test, blocked, and parent cases that matter to your workflow.
If a field is missing or not updating, check the Vansah mapping, Jira field context, screens, permissions, and status options. Refresh the testing view and check the saved Jira value again.
If the transition behaves unexpectedly, check the workflow and transition actually used by that work item, the field selected in the rule, its exact value, and whether the workflow changes were published.
Do not set a passing default merely to bypass the check. A default Jira field value is not evidence that tests have run.
Video overview: Jira workflow validators with Vansah test results. The video shows an earlier Jira/Vansah layout; follow the current configuration labels above.