Uploaded image for project: 'Admin Experience'
  1. Admin Experience
  2. AX-715

After site rename, old name redirect only works on browser and not any other API

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      N/A

            [AX-715] After site rename, old name redirect only works on browser and not any other API

            Rodrigo B. made changes -
            Component/s Original: Site Rename [ 61300 ]
            Component/s New: Org Management - App URLs - Update URL [ 80162 ]
            Key Original: ACCESS-1779 New: AX-715
            Support reference count Original: 10
            Description Original: h3. Issue Summary

            After a site is renamed, the old URL should still work. 
            However, it only works as intended via the browser. API calls only show redirects. 
            h3. Steps to Reproduce
             * Perform a site rename as described [here|https://support.atlassian.com/organization-administration/docs/update-your-product-and-site-url/]
             * Try calling an issue using both the old and new site names via the browser.
            {*}Old{*}: [https://old-name.atlassian.net/rest/api/3/issue/]<issuekey>
            {*}New{*}: [https://new-name.atlassian.net/rest/api/3/issue/]<issuekey>
            {*}Result{*}: Both give the result, the old-name link redirects to the new name.

             * Try calling the issue using the [GET issue|https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-get] endpoint via Postman.
            {*}Old{*}: [https://old-name.atlassian.net/rest/api/2/issue/]<issuekey>
            {*}New{*}: [https://new-name.atlassian.net/rest/api/2/issue/]<issuekey>
            {*}Result{*}: The new-name API call works, but the old-name API only shows 302 redirects. 

            h3. Expected Results
             * API calls (ie via Postman or terminal) should also show the output the same as in the browser. 

            h3. Actual Results
             * {*}Old{*}: [https://old-name.atlassian.net/rest/api/2/issue/]<issuekey>
            {*}New{*}: [https://new-name.atlassian.net/rest/api/2/issue/]<issuekey>

            !image-2023-08-03-14-28-05-703.png!


            h3. Workaround

            This is the intended behavior. For API calls, please use the new site name for calling endpoints. 
            New: N/A
            Project Original: Atlassian Guard [ 18910 ] New: Admin Experience [ 24210 ]
            SET Analytics Bot made changes -
            Support reference count Original: 9 New: 10
            SET Analytics Bot made changes -
            Support reference count Original: 8 New: 9
            SET Analytics Bot made changes -
            Support reference count Original: 7 New: 8
            SET Analytics Bot made changes -
            Support reference count Original: 5 New: 7
            SET Analytics Bot made changes -
            Support reference count Original: 4 New: 5
            SET Analytics Bot made changes -
            Support reference count Original: 3 New: 4
            Cole Norman made changes -
            Labels New: guard-s7
            SET Analytics Bot made changes -
            Support reference count Original: 2 New: 3
            SET Analytics Bot made changes -
            Support reference count Original: 1 New: 2

              Unassigned Unassigned
              02a6ae09c2cc Cecille Maquito
              Votes:
              6 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated: