Documentation for GreenHopper 6.1.x. Documentation for other versions of JIRA Agile is available too.
GreenHopper is now called JIRA Agile. Learn more.


(info)本ページの内容はスクラムボードにのみ適用されます。 カンバンボードを使用している場合は、バージョン(カンバン)をリリースする を参照してください 。

On the final day of the sprint the team will complete the sprint — this will usually occur immediately prior to the sprint demo and retrospective. Any issues not completed at the end of the sprint will be returned to the backlog (or to the next planned sprint, if you have one) as they did not meet the team's definition of "Done".

To end the active sprint,

  1. Login to JIRA.
  2. 上部ナビゲーションバーで Agile リンクの下矢印をクリックし、表示されるドロップダウンメニューから目的のボードを選択します。

  3. Click Work.
  4. Click the cog dropdown, next to the sprint name, to display a dialog box (see Screenshot 1 below).
    (info) Or, if you are using GreenHopper 6.0.1 or earlier, click the arrow icon at the top of the Done (rightmost) column.
  5. 希望する場合は、スプリント名、開始日および終了日を編集できます。
  6. Click the Complete Sprint button.
    (info) You will need to have the JIRA 'Project Administrator' permission in the project(s) whose issues are included in the sprint.
    (info) When you try to close a sprint, and you have parent issues not Done but all sub-tasks are Done, or visa-versa, you will be prompted to make the parent Done before continuing. For issues to be interpreted as 'Done' on your Scrum board their status needs to be mapped to that column, so if you're receiving errors for parents or sub-tasks that you believe are in fact Done, ensure that they are mapped correctly.
  7. You will be taken to the Sprint Report. Your issues will move out of Work mode. Any incomplete issues will move back into the backlog and will be visible in Plan mode.

 (info) 注意:

  • スクラムチームは完了した課題をトラッキングするのに、スプリントではなくバージョンを使用するのが普通であるため、スプリントがクローズされた日付で課題がマークされることはありません。
  • Once a sprint is closed, you cannot re-open it. If you need to view the contents of the sprint again, you can select that sprint in the Sprint Report.
  • You can find issues belonging to all closed sprints by using the closedSprints() function. For details, please see the JIRA JQL documentation.

Screenshot 1: Completing a Sprint



Many Scrum teams don't release a version at the end of a sprint, but if you need to, it's easy to do. In the Completed Issues section of the Sprint Report, just click View in Issue Navigator. You can then use JIRA's Bulk Edit to assign all of the issues to the relevant version (for details, please see the JIRA documentation on Bulk Operations). Note that you will not be able to do this if your "Done" column sets an issue's status to "Closed", as issues are not editable once they are "Closed" (but "Resolved" is fine). Also note you can only Bulk Edit the "Fix Version" for issues from one project at a time.