A user’s access to Vansah depends on the Jira space they can access, whether Vansah is enabled for that space, and the permission needed for the action they want to perform. Use the checks below when Vansah is missing or a testing action is unavailable.
Start with these checks
Check | What to confirm |
Jira access | The user is signed in to the correct Jira site and can browse the Jira space. |
Vansah availability | Vansah is installed, available under the site’s license, and enabled for the Jira space. |
Vansah action permissions | The user meets the permission for the exact action, such as viewing, creating, executing, or deleting Test Cases. |
Feature availability | The requested feature is enabled and included in the available subscription, where applicable. |
Check whether Vansah is enabled for the space
A Jira administrator can review workspace availability:
In Jira, open Apps → Vansah.
Select Configure.
Review Default behaviour and the Excluded spaces or Included spaces list. Confirm the affected Jira space has the intended availability.
After a successful settings change, return to the Jira space and reload Vansah.
The screenshot shows the Configure entry point in an earlier layout. Follow Enable or Disable Vansah for Specific Jira Spaces for the current availability controls. Check the saved workspace settings rather than assuming Vansah is enabled for every space.
Check permissions for the action
Vansah permissions can be configured with Jira groups. When no groups are selected for an action, Vansah uses its default Jira permission check. For supported actions, the creator of the item may also retain access.
Permission configuration | How access is checked |
No Jira groups selected | The action uses its default Jira permission and any applicable creator rule. An empty group selection does not block everyone. |
One or more Jira groups selected | The user needs membership in at least one selected group, or an applicable Allow Creator rule. |
Separate administrator requirement | Some settings require Jira administrator or Jira space administrator access even when the user can perform other testing actions. |
For example, permission to view Test Cases does not by itself grant permission to delete them or manage Space Settings. See Default Jira Permissions for Vansah for the default checks.
Review the space’s Vansah permissions
A Jira administrator or Jira space administrator can review the configuration:
Open Vansah in the affected Jira space.
Open the Settings gear and select Settings and Compliance.
Select Space Settings, then Permissions.
Find the exact action the user needs. Review its selected Jira groups and any Allow Creator option.
Confirm the user’s group membership or applicable Jira permission. After changes, reload the affected screen and try the action again.
See Manage Vansah Permissions with Jira Groups for configuration steps, or Open Vansah Space Settings if you cannot find the permissions page.
Troubleshoot the user’s access
What the user sees | What to check |
The Jira space is unavailable | Ask a Jira administrator to check the user’s access to that space. |
The space is visible, but Vansah is missing | Check Vansah installation, license, and saved availability settings for the space. |
Vansah opens, but an action is unavailable | Check the permission for that specific action, the user’s Jira groups, and any creator rule. |
Space Settings is unavailable | Check Jira administrator or Administer space permission. |
A feature is missing for an otherwise authorized user | Check whether it is enabled and available with the subscription. |
Access still fails after a change | Reload the screen. Give your administrator the Jira space key, the action attempted, and the exact error message. |