Documentation for JIRA 5.2. Documentation for other versions of JIRA is available too.

Versions are points-in-time for a project. They help you schedule and organise your releases. Once a version is created, and issues are assigned to it, the following reports are useful:

The Change Log and Road Map reports are driven by the 'Fix For Version' field on each issue.

バージョンは以下のことが可能です。

  • 追加 - 課題を配置する新しいバージョンを作成する。
  • Released — mark a version as released. This changes the Road Map report, Change Log report and some issue fields' drop-downs. If you have integrated JIRA with Bamboo, you can also trigger builds when releasing a version.
  • スケジュール変更 - バージョンの順序を並び替える。
  • Archived — hide an old version from the Road Map and Change Log reports, and in the JIRA User Interface.
  • マージ - 複数のバージョンを一つにまとめる。

On this page:

プロジェクトのバージョンを管理する

  1. Log in to JIRA as a project administrator.
    (info) A project administrator is someone who has the Administer Project project-specific permission, but not necessarily the JIRA Administrators global permission.
  2. Choose Administration at the top right of your screen. Then choose Projects from the menu bar and select the name of the project of interest. Otherwise, choose your project from the Projects list or Project Categories. The Project Summary page is displayed (see Defining a Project).
    (tick) Keyboard shortcut: g + g + start typing project
    The Versions section of the Project Summary page shows a summary of versions in your project and the scheduled release date for each version (see Screenshot 1 below).
  3. Click the More link to display the Versions page (see Screenshot 2 below), which shows a list of versions and each version's status. From here you can manage the project's versions as described below.


Screenshot 1: The 'Versions' section of the 'Project Summary' screen


Screenshot 2: The 'Versions' screen

バージョン ステータス

各バージョンは、次の 4 つのうち、いずれかのステータスを持ちます。

  • リリース済み - バンドルされたパッケージ
  • 未リリース -オープン パッケージ
  • アーカイブ済み - 半透明のパッケージ
  • Overdue— the release date is highlighted

    The status affects where the version appears in drop-down lists for version-related issue fields ('Fix For Version' and 'Affects Version').

Adding a new version

  1. The 'Add Version' form is located at the top of the 'Versions' screen (see Screenshot 2 above).
  2. バージョンの名前を入力します。次のような名前が入力可能です。
    • simple numeric, e.g. "2.1", or
    • complicated numeric, e.g. "2.1.3", or
    • a word, such as the project's internal code-name, e.g. "Memphis".
  3. Optional details such as the version description and release date (i.e. the planned release date for a version) can be also be specified.
  4. Click the 'Add' button. The version management list is updated immediately, with the newly created version added at the top of the list — you can drag it to a different position if you wish, by hovering over the 'drag' icon at the left of the version name:

バージョンをリリースする

(info) Before you begin: If you have integrated JIRA with Atlassian's Bamboo, you can trigger a Bamboo build to run automatically when releasing a version in JIRA. The version will only be released if the build is successful. See these alternate instructions: Running a Bamboo Build when Releasing a Version.

  1. On the 'Versions' screen (see Screenshot 2 above), hover over the relevant version to display the cog icon, then select 'Release' from the drop-down menu.
  2. このバージョンを「修正」バージョンとする課題がある場合は、必要であれば、JIRA で「修正」バージョンを変更できます。変更の必要がなければ、これらの課題を修正することなく操作を完了します。

(info) To revert the release of a version, simply select 'Unrelease' from the drop-down menu.

Archiving a version

  1. On the 'Versions' screen (see Screenshot 2 above), hover over the relevant version to display the cog icon, then select 'Archive' from the drop-down menu.
  2. バージョン一覧で、半透明のアイコンはバージョンが「アーカイブ済み」ステータスであることを示しています。利用可能な操作一覧は、「アーカイブ解除」操作によって置き換えられます。アーカイブを解除しない限り、このバージョンにこれ以上変更を加えることはできません。また、課題の影響バージョンおよび修正バージョン フィールドから既存のアーカイブ済みバージョンを削除したり、新たなアーカイブ済みバージョンを追加したりできません。

(info) To revert the archive of a version, simply select 'Unarchive' from the drop-down menu.

Merging multiple versions

Merging multiple versions allows you to move the issues from one or more versions to another version.

  1. On the 'Versions' screen (see Screenshot 2 above), click the 'Merge' link at the top right of the screen.
  2. The 'Merge Versions' popup will be displayed. On this page are two select lists — both listing all un-archived versions. In the 'Merging From Versions' select list, choose the version(s) whose issues you wish to move. Versions selected on this list will be removed from the system. All issues associated with these versions will be updated to reflect the new version selected in the 'Merge To Version' select list. It is only possible to select one version to merge to.
  3. Click the 'Merge' button. If you are shown a confirmation page, click 'Merge' again to complete the operation.

Editing a version's details

  1. On the 'Versions' screen (see Screenshot 2 above), hover over the relevant version to display the pencil icon.
  2. これによって、バージョンの名前や説明、リリース日を編集できるようになります。
  3. Click the 'Update' button to save your changes.

Deleting a version

  1. On the 'Versions' screen (see Screenshot 2 above), hover over the relevant version to display the cog icon, then select 'Delete' from the drop-down menu.
  2. This will bring you to the "Delete Version: <Version>" confirmation page. From here, you can specify the actions to be taken for issues associated with the version to be deleted. You can either associate these issues with another version, or simply remove references to the version to be deleted.

Rescheduling a version

Recheduling a version changes its place in the order of versions.

  • On the 'Versions' screen (see Screenshot 2 above), click the icon for the relevant version, and drag it to its new position in the version order.

参考資料

4 Comments

  1. Pavel Bulanov

    Is there any way to have a workaround to allow creation of versions not only for Project Administrators?

    We use versions as build number to indicate which build (version) issues is resolved for. Normally at least build integrator needs to create new version in Jira, and it might be even any developer could do that. Same time, I don't want them to be able to add / remove people from the project, which permission is also granted with project administration right. Is there a way to overcome this?

    1. SusanA

      Hello Pavel, I am not aware of any way for a non-Project Administrator to do this. Our support team may be able to offer suggestions for other ways to accomplish this, you can click the Get Support link for further advice. Good luck!

  2. Anonymous

    We upgraded to greenhopper 6. In the earlier version that we used, the fixed for versions were the same as the sprint names. We would create a version to represent each sprint. A version in the regular JIRA view could be mapped directly to a sprint in the Greenhopper view. From the documentation on versions above it appears that versions are not at all mapped to sprints. Why were sprints decoupled from versions in the new Greenhopper? Why is this good for me?

     

  3. Anonymous

    We would like to migrate data from another system to trackSpace. At the moment we've got >1000 versions in the old system. It would be possible to export a CSV-file with all versions from the old system. Unfortunatley I didn't find a way to mass create / mass import different versions at the same time.

    Is there a way to import versions into trackSpace from e.g. a CSV-file? I've seen the CSV-import functionality. To my understanding the CSV-import-functionality is working for issues only!?