How to Identify Issues that belongs to any Sprint in JIRA

お困りですか?

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

コミュニティに質問

This article requires fixes

This article has been Flagged for fixing. Use caution when using it and fix it if you have Publisher rights.

プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Fisheye および Crucible は除く

目的

The purpose of this article is to show how to identify issues with Sprint and those that does not belong to any Sprint. This can be done via JQL and SQL.

ソリューション

  1. All the issues that have been put into some sprint:

    1. JQL:

      Sprint is not EMPTY
    2. SQL:

      select ji.id, concat(P.pkey,concat('-',ji.issuenum)) from jiraissue ji join project P on P.id = ji.project join customfieldvalue cv on ji.id=cv.issue join customfield cf on cf.id=cv.customfield where cf.cfname='Sprint'
  2. All the issues that have not been put into any sprint:

    1. JQL:

      Sprint is EMPTY
    2. SQL:

      select I.id,concat(P.pkey,concat('-',I.issuenum)) from jiraissue I join project P on P.id = I.project where I.id not in (select ji.id from jiraissue ji join customfieldvalue cv on ji.id=cv.issue join customfield cf on cf.id=cv.customfield where cf.cfname='Sprint')
最終更新日 2022 年 11 月 7 日

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

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