After changing an existing Jira Cloud site’s URL, open Vansah from the renamed site to refresh its connection. Vansah uses the Jira Cloud site identity and updates its stored site address when it receives the new address from Jira.
Before you begin
An organization administrator must perform the Atlassian site URL change.
Check Atlassian’s URL change eligibility and limitations for your site.
Confirm the site you intend to rename and note its existing URL.
These steps cover changing the subdomain of an existing site, such as example-team.atlassian.net. For a branded domain, follow Atlassian’s separate custom-domain setup.
1. Change the site URL in Atlassian Administration
Open Atlassian Administration and select the correct organization.
Select Apps → App URLs.
Find the site and select Update URL.
Enter the new subdomain and select Continue.
Review which apps will use the new address, then select Update.
Wait for Atlassian to complete the update.
Atlassian says the change may take up to five minutes. Follow its Update an app URL subdomain guide for the full procedure.
2. Open Vansah from the new Jira URL
Open Jira using the updated site address and sign in.
Select Apps → Vansah. You can also open a Jira work item where the Vansah panel is available.
Allow Vansah to load. If authorization is requested, complete the normal authorization flow for that site.
Open a known Jira space and check an existing Test Case or Test Run.
The screenshot highlights Apps → Vansah in an earlier landing-page layout. You do not need to manually enter the new Jira URL in a Vansah field for this refresh.
3. Check links and integrations
Open a Test Case and a Test Run from the renamed site to check their links and details.
Update bookmarks and any tools that store the old Jira address.
If a script calls Jira’s REST API directly, update it to the new Jira URL. Browser redirects do not guarantee that an API request will continue to authenticate.
Atlassian explains the browser redirects and REST API impact in its site URL update guide.
If you use Vansah for Confluence
Open a Confluence page that uses Vansah and check that it can still access the intended Jira site. If it reports a connection problem, review Connect Vansah for Confluence to Jira and verify the connected Jira app and account access.
If the connection remains unavailable, contact Vansah support with the old and new site URLs and the error you see.
Troubleshoot after the change
Issue | What to check |
Vansah does not load | Open the updated Jira URL directly, confirm that Jira works, then reopen Apps → Vansah and complete any requested authorization. |
A user cannot open testing data | Check the Jira site and Jira space, then verify the user’s Jira and Vansah permissions. A site rename does not grant new access. |
An integration receives an authentication error | Check whether it is still calling Jira’s old REST API URL and update that configuration. |
You see an unexpected workspace or missing data | Confirm that the new address belongs to the same renamed Jira site. Contact Vansah support before creating replacement testing data. |
A Confluence report cannot connect | Review the Confluence-to-Jira connection and the signed-in account’s Jira access. |
For help, contact Vansah and include the old URL, new URL, affected Jira space, and exact error message.