REST API calls failing with error 4xx response code after Cloud site is renamed

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

プラットフォームについて: Cloud のみ - この記事は クラウド プラットフォームのアトラシアン製品に適用されます。

問題

As an administrator, you may have some scripts or webhooks configured that utilise Cloud REST API calls to perform operations/actions on your Jira site (E.g: Create issues, update issues).

Recently, your Cloud site went through a URL name change – after the site renamed, all the REST API calls started failing with errors with a 4xx response code (E.g: 401, 403, 404)

原因

This is due to the tool/scripts used to perform the REST API calls still trying to reach the old site URL – currently, Jira Cloud does not have the ability to auto-redirect REST API calls from the old site name to the updated site name. 

There is a bug report raised for this limitation which can be tracked on:

回避策

After a Cloud site has gone through a renaming, make sure to update the REST API calls used in your environment with the new site name. 



最終更新日 2024 年 5 月 30 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.