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

(info) This page only applies to Scrum boards. If you are using a Kanban board, please see Releasing a Version (Kanban).

チームはスプリントの最終日にスプリントを完了します － これは通常スプリントのデモやふりかえり直前に実施します。スプリントの終了時に完了していない課題は、チームが定めた " 完了 " の定義を満たさないため、次の計画スプリントに移されます。次の計画スプリントがない場合は、バックログに戻されます。

To end the active sprint,

  1. Login to JIRA.

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

  3. Click Work.
  4. スプリント名の横のドロップダウンをクリックして、ダイアログボックスを表示します（下のスクリーンショット 1 を参照）。
  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.

 

 



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Tweet, blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.