Change the space key in Jira’s space settings, then open Vansah in that Jira space so Vansah can detect the new key and update its stored references. You do not change the Jira space key in Vansah settings.
Before you begin
Have an organization, site, or Jira administrator make the change.
Choose the new key and let your team know. Record the old key so you can check saved reports and integrations afterward.
Review scripts, automation, and external integrations that contain the old key. Vansah’s synchronization does not rewrite configuration in other tools.
Jira keeps previous space keys so existing Jira work item links can continue to resolve. Saved queries and integrations still need review. See Atlassian’s guidance on changing space keys.
1. Open the space settings
Open your Jira space, select More actions (three dots) beside the space name, and choose Space settings.
Administrators can also use the route shown below: open the Settings gear, select Spaces under Jira admin settings, and open Space settings for the relevant space.
2. Save the new key
Open Details.
Enter the new value in Space key. Choose an available key with at least two characters, beginning with an uppercase letter and containing only uppercase letters or numbers.
Select Save.
3. Open Vansah and check the change
Open Vansah in the renamed Jira space, or open the Vansah Test Management panel in one of its Jira work items. This gives Vansah the updated Jira space information.
Reload the view and check a Test Case key. For example, after changing DEMO to SHOP, DEMO-C46 is displayed as SHOP-C46.
Open the dashboards, saved Vansah reports, and Confluence pages that use the space. Check their selected space, work items, and results.
Update scripts or integration settings that still send the old space key or old readable Test Case keys.
In API requests, the field names projectKey and project.key stay the same. Their values refer to the Jira space key, so use the new value.
What Vansah updates
When Vansah detects the change for an existing Jira space, it updates its stored space key, linked work item references, and supported space and work item selections in gadget configurations. The synchronization also handles those selections in saved gadget configuration versions and saved report settings.
Test Case keys use the stored Jira space key as their prefix. You do not need to rename each Test Case individually.
Check the reports you rely on after the change. The automatic update covers specific saved references; it does not guarantee that every custom query, text label, or external link containing the old key is rewritten.
If you still see the old key
Open Vansah directly in the affected Jira space, then reload the page. A report opened elsewhere may not yet have triggered the space update.
If one report still points to the old space or work items, review its saved selections and choose the current values.
If an automation request fails, check the space key and readable keys in its configuration.
If the space remains out of sync, contact Vansah with the old key, new key, affected report or page, and a screenshot.