Vansah can update Jira custom fields with a work item’s testing status and execution metrics. Configure the field mappings in Vansah, then use those Jira fields in your workflow rules. Enabling the fields does not create a transition rule automatically.
Before you begin
Sign in as a Jira administrator.
Use a Vansah subscription that includes workflow field support.
Have a Jira work item with linked Test Cases available to verify the field values after setup.
1. Enable the custom fields
In Jira, open Apps → Vansah and select Configure.
Find Workflow validator and turn on Enable Vansah Custom Fields.
If Vansah prompts you to create missing fields, review the listed field names and select Create.
Wait for the success message, then check the field mappings below the control.
The screenshot shows the field controls in an earlier Configure layout. The current status section is labeled Test Result Status; its default Jira field name is Vansah TR Status.
2. Check or choose the Jira field mappings
Vansah value | Default Jira field | Field type |
Test Result Status | Vansah TR Status | Single-select field |
Pass rate | Vansah Pass Rate | Number field |
Fail rate | Vansah Fail Rate | Number field |
Execution coverage | Vansah Coverage | Number field |
Expand a field section to see its mapped Jira field.
If you need to use an existing field, search the compatible Jira fields and select the correct one.
Review the confirmation and select Confirm. Repeat for the other values you need.
Check that each required section shows a mapped field instead of Not mapped.
Vansah filters the choices by field type. Use a separate Jira field for each value. When mapping the status field, Vansah can add its test-result options to that field.
Rate and coverage fields store numeric percentages, such as 75 for 75%. Coverage measures completed tests as a share of planned tests. Pass rate excludes completed N/A tests.
Understand Test Result Status
The status summarizes the group of linked Test Cases. These are the default values; customized test-result names can appear instead.
Default value | Meaning |
No-Test-Cases | No linked Test Cases are included in the calculation. |
Untested | Test Cases are linked, but testing has not started. |
Passed | All tests are complete, at least one passed, and none failed. Completed N/A tests can also be present. |
Failed | All tests are complete and at least one failed. It does not mean every test failed. |
Passed-In-Progress | Some tests have passed, but testing is not complete. |
Failed-In-Progress | A failed result is present while testing is not complete. |
N/A | All tests are complete with N/A results. |
N/A-In-Progress | N/A results are present while testing is not complete. |
Blocked | At least one included Test Case is blocked. |
These are aggregate outcomes. Open the work item’s Vansah Report tab to investigate individual counts and results.
3. Verify the values in a work item
Open a Jira work item with linked Test Cases.
Review its Vansah Report tab and the mapped Jira fields. If a field is not visible, ask your Jira administrator to check its field context and work item layout.
Record or update a test result, then reload the work item and check that the relevant field values update.
Confirm which status names and metric values your workflow should accept.
If you use Enable Child Work item Test Result Status, check the parent and child field values together. This option makes child results relevant to the parent’s workflow fields. Verify the intended behavior before using a parent field to control transitions.
4. Use the mapped fields in a workflow
Configure the transition rule in Jira after the field values are working. For example, your team may require the mapped test-status field to equal Passed before a work item can move from Testing to Done.
Use the rule supported by your Jira workflow editor or validator app, select the mapped Jira field, and use its actual status value. Publish the workflow changes and test both an allowed and a blocked transition.
For Jira’s field-value condition setup, see Allow workflow transitions based on field values. A rule that only requires the field to be nonempty does not check that testing passed.
If a field is missing or does not update
The workflow section is missing: Check the subscription and your Jira administrator access.
A Jira field is missing from the picker: Check its type. Status needs a single-select field; rates and coverage need number fields.
A value stays unchanged: Check the saved mapping and field context, then compare the relevant work item’s test results. If it still does not update, share the work item key and mapping screenshot with Vansah support.
A transition still works when testing has failed: Check that the rule is published, applies to that transition, and checks the mapped field’s value. Enabling the Vansah fields alone does not restrict transitions.
Before disabling the integration
Turning off Enable Vansah Custom Fields removes the Vansah field integration. It does not delete the Jira custom fields or remove rules you already configured in Jira. Review those rules before disabling updates so they do not rely on stale field values.