Filters break after renaming issue types at the Epic level

お困りですか?

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

コミュニティに質問

robotsnoindex


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


要約

Existing JQL filters that include issue types (such as the "issuetype = epic" clause) break when organizations rename issue types at the Epic level in company-managed projects.

環境

This applies to Cloud only. 

診断

If:

  • your site uses JQL filters that reference the issue type (such as the issuetype = epic clause) and

  • your administrator recently renamed the issue type

Then:

  • your filter won’t return any results.

原因

JQL looks for issue types according to their name. If an administrator renames an issue type at the Level 1 hierarchy, the query in your filter no longer matches the name of the issue type.

ソリューション

  1. Revert the change to the status names.  Once reverted, the JQL filters should then result the expected results as they previously did.
  2. Update your JQL filters to include the new status name of the issue type previously called Epic.  If you want other issue types that sit at the Level 1 hierarchy level to be included, you’ll need to add them to your queries as well.





最終更新日: 2025 年 2 月 21 日

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

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