Documentation for JIRA 6.3 EAP developer (EAP) releases only. Not using this? See below:
(JIRA 6.2.x documentation | JIRA OnDemand documentation | earlier versions of JIRA)

Skip to end of metadata
Go to start of metadata

Versions are points-in-time for a project. They help you schedule and organize 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.

Versions can be:

  • Added — create a new version against which issues can be aligned.
  • 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.
  • Rescheduled — re-arrange the order of versions.
  • Archived — hide an old version from the Road Map and Change Log reports, and in the JIRA User Interface.
  • Merged — combine multiple versions into one.

On this page:

Managing a project's versions

  1. Log in to JIRA as a project administrator.
  2. Choose > Projects. The Project Summary page is displayed (see Defining a Project).
    (tick) Keyboard shortcut: g + g + start typing project
  3. Choose Versions in the left menu. The Versions page is displayed, showing a list of versions and each version's status. From here you can manage the project's versions as described below.

    Screenshot: The 'Versions' screen

Version status

Each version can have any of the following four statuses:

  • Released — a bundled package
  • Unreleased — an open package
  • Archived — a semi-transparent package
  • Overdue— the release date is highlighted

    Icon

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

Add a new version

  1. The Add Version form is located at the top of the 'Versions' screen.
  2. Enter the name for the version. The name can be:
    • 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 (text not HTML), start date and release date (i.e. the planned release date for a version) can be also be specified.
  4. Click the Add button. You can drag the new version to a different position by hovering over the 'drag' icon at the left of the version name.

Add a start date

If specified, the Start Date is used by the Version Report. This gives you a more accurate report in cases where you might plan a version many weeks (or even months) in advance, but not actually commence work until closer to the release date.

Release a version

(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, hover over the relevant version to display the cog icon, then select Release from the drop-down menu.
  2. If there are any issues set with this version as their 'Fix For' version, JIRA allows you to choose to change the 'Fix For' version if you wish. Otherwise, the operation will complete without modifying these issues.

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

Archive a version

  1. On the 'Versions' screen, hover over the relevant version to display the cog icon, then select Archive from the drop-down menu.
  2. The version list indicates the version 'archived' status with a semi-transparent icon. The list of available operations is replaced with the 'Unarchive' operation. No further changes can be made to this version unless it is un-archived. Also it is not possible to remove any existing archived versions from an issue's affected and fix version fields or add any new archived versions.

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

Merge multiple versions

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

  1. On the 'Versions' screen, 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.

Edit a version's details

  1. On the 'Versions' screen, hover over the relevant version to display the pencil icon.
  2. This will allow you to edit the version's Name, Description and Release Date.
  3. Click the Update button to save your changes.

Delete a version

  1. On the 'Versions' screen, 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.

Reschedule a version

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

  • On the 'Versions' screen, click the icon for the relevant version, and drag it to its new position in the version order.

See also

40 Comments

  1. In the section Adding a New Version I see this instruction:

    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.

    I can't seem to find any drag options - only the up/down arrows and the move to top or move to bottom curved arrows.  The drag and drop feature would be fantastic as keeping the Fix Versions in the proper order is an absolute nightmare with having to edit and chose a position based on another fix version.  Better yet would be if we could just tell Jira to keep them in date order ....

    1. Thanks Carrie, I've clarified the instructions.

      1. Maybe I'm missing something because when I try to drag and drop the icon to the left of the FixVersion Name that looks like a package it does nothing besides give me the circle with a slash through it.  Is this something that is Jira version specific?  If not then I need to have a chat with our admin about enabling features.  Also your vgrabber.png image inline is blank.

        1. Hi Carrie,

          Have you confirmed whether or not you have the 'Administer Project' permission for the project you are administering? (This permission would typically be designated to your user account via group membership or a project role AND via the permission scheme applied to the project you're administering.)

          If you do not have this permission for the project you are administering, you will not be able to manage versions for your project and the drag icon will not be visible.

          Cheers,

          Giles.

          1. Yes I have do have Admin for these ... I think however I figured it out.  I searched through the Confluence Wiki pages and found reference to this topic for an older version of Jira that had a screen shot that looked like what we have.  Seems that this feature of drag and drop for organizing the Fix Versions is Jira version specific.  I have brought it up to my team that we are using an older version and need to upgrade to get this management feature and it was put high on the list of reasons for upgrading our Jira.

  2. Anonymous

    How can custom fields be added to a version? For example, if I need to track progress through phases or milestones for external tracking purposes? Would this require writing a plugin?

    1. Anonymous

      I'd be interested in this feature as well.  I'd also like to be able to remove the "Build & Release" option as we aren't using Bamboo.

  3. I would like to see the status of each version. 

    Can I add the status column on the Versions page?

  4. Anonymous

    My name is Marcos Lima. I would like change start date and end date for a version. Where can I do that?

     

    Thanks 

    1. Anonymous

      I've found a way using Greenhopper.  But I'm not sure which permission make the start date/end date/release date edit available

  5. Anonymous

    I had got a desire to make my own firm, but I did not earn enough of money to do it. Thank heaven my fellow suggested to utilize the personal loans. Hence I received the student loan and realized my old dream.
  6. Is there any non-GUI way to release a Version?  Is there an option to have a Version auto-release on the releaseDate?

    Thanks

    1. I've been wondering about this too.  The dialog that comes up when you click "Release" takes several minutes and (I can only view this as a bug) pretty much locks up my browser while I wait).

      I was hoping to do this with the JIRA CLI, but it doesn't seem possible.  I'm struggling to understand the REST API to see if it's doable there.

  7. Anonymous

    Thanks a lot! It was of great help!

  8. Anonymous

    I have created versions for a project, but in the "Create Issue" form, there is only option to select "Affects Version". The "Fix Version" is not appearing. How do I add this? Agile view is not useful without it!

    Thank you!

    1. +1 I would like to know how to edit "Affects Version" as well.

  9. Anonymous

    Is there a possibility to manage versions without the "administer-projects" permission?

    Can I give that specific permission to some users who are not project-administrators?

    Thanks!

    1. Anonymous

      I wish this existed too. We have some people we just want to be able to manage versions & components for one specific project. 

      1. Anonymous

        And I clearly should read better, just figured that you only put it on the project(s) you want the users to administer...duh.

  10. Anonymous

    How about the ability to add the start date to the version so that the classic burndowns work properly, otherwise they start at todays date, not particularly useful!

    1. Anonymous

      ability to add a start date to versions would be very useful for us.

      1. Anonymous

        Any update on this? We would really need a version start date! Still not possible?

  11. I am in the midst of creating/dividing my application in to different versions.   My question relates to the assignment of an issue to more than one version.  Rather than talk in the abstract, I will try to outline this in a Use Case

    Use Case.

    Issue A (and its sub issues) relates to version 1 and version 2 of my software, so I tag Issue a with both version tags (1 and 2)  in the version dialog.

    Now when I go to close Issue A as it relates to version 1 (we did the Issue A sub tasks associated with version 1), how does this impact the relationship between Issue A and version 2, does Issue A remain open when viewing Version 2, or is it automatically closed in version 2  as a result of closing it in version 1?   In other words, am I required to break down Issue A into two discreet issues, one for version 1 and one for version 2.  My initial assumption is that I don't, otherwise why would I be able to assign an issue to more than one version

     

    Thanks

  12. Hey,

    is there a way to automatically archive all the version numbers that doesn't have any open bugs remaining in the database ?

    Thanks for your help

  13. As of JIRA 5.2.1, Versions don't work that way at all. There is a '...add X more' link, the result is not a table, and there appear to be no mechanisms for adding Versions.t

    1. Hi Paul,

      I just tried viewing the Versions administration screens in JIRA 5.2.1 and it matches the documentation above. Can I ask you to log a request with our support team at https://support.atlassian.com for assistance?

      Kind Regards,
      Andrew

      1. Anonymous

        tilyingomelegeMy bad. From the Project Summary page it doesn't work as described. From Project Configuration it does

  14. We recently migrated to GreenHopper 6.1 and JIRA 5.2.  We are now using Sprints and the new Task Boards for managing our work.  Previously we used fixVersion to track our Sprint numbers.  Frequently we are finding the need to access 'older' stories that were completed in our prior version of Jira.  Is there an easier way than using the 'Classic' view to take a look backwards?  Everytime we go to the 'Classic' view, we get the "no longer supporting changes" message which makes some of our folks believe this entire 'Classic' view process will be going away soon.  Thanks!

  15. 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?

    PS. I first posted this comment to JIRA 5.2 page as it seems to be last released version, but here it's more "living" page.

    1. You can create a group and use it in a Permissions scheme to grant Project Administration rights. Since you need JIRA admin rights to do things with groups and schemes I do not beleive this gives them the ability to affect project members.
      (Atlassian Answers would be a better forum for this kind of question)

  16. Anonymous

    I cant see the add\manage versions on a specific project. Is this due to the permissions assigned.. If yes, how do i grant permission to the specific project in which i want to add\manage versions.

    1. Short answer, yes. by default the Project Lead has the 'administer project' privilege. To adjust this you need to be part of the jira-administrators group. Check what permission scheme the project is using. Then an administrator can grant you the privilege you need or add you to the group that has it. I would recommend not changing the default schemes. make a copy and change them as needed .

  17. How to Create a single version and assign it two different projects in JIRA.

    Lets say I have ProjA, ProjB and ProjC and all these projects have issue related to one version i.e ver1. So instead of visiting and creating version for each project, is there a way to create and assign versions to Projects from an admin level ?

    This will be really helpful as the way we are handling projects in JIRA is that one version affects many projects in JIRA.

  18. Anonymous

    If version is archived, can it still be used via API?

    For example, we have a sync tool with other tracking system, run by our customer. Let's say a version is archived and hidden from JIRA GUI. Will this version be still available for a synchronization tool to create an issue via API and assign it to that version?

  19. Anonymous

    My JIRA 6.0.4 version release dates are different from the Manage Versions page to the Version page.  My Version page states that the Release Date is 24/Sep/2013 and the Manage version page states that the Release Date is 25/Sep/2013.  How can I get the Version page to have the same release date as the Manage Version page?

  20. If you want to enable managing versions for the project lead, in JIRA 5.2.5 it does not seem to be enough to grant the project permission "Administer Project" to the project lead:

    The following configuration is set:

    • User Alice is in Group "jira-users". Alice is not in Group "jira-administrators".
    • There is one Permission Scheme "Default Permission Scheme". In this permission scheme the Project Permission "Administrate Projects" is given to group "jira-administrators", Project Lead and Project Role "Administrators".
    • In the Project PROJ Alice is set as project lead. No other role assignements are made in the project.
    • Default Permission Scheme is selected for PROJ.

    Expectation: As Alice is the project lead and project lead has the permission Administer Project she should be able to manage versions.

    Actual situation: Alice does not see the button on the Versions-screen nor does she see the "Administer Project" button on the overview screen of the project.

    Quick solution: When I give alice the role "Administrators" in the project, she sees the buttons and can manage versions.

  21. Anonymous

    Can I sort by the Version's due date?

    • project p1 is numbered like 1.11 with the minor version updated regularly
    • project p2 is numbered like 22.0 with the major version updated regularly

    p2 v22.0 is due before p1 v1.11, so I want tasks for p2 v22.0 to appear before p1 v1.11

    Sometimes I can sort DESC on fixVersion which will put 22.0 above 1.11 - but if tasks exist for 22.1 or 1.12, it doesn't help

  22. Ist there any reason that there is no possibility to sort/filter the list of versions? The only way would be to manually (drag&drop) sort it which is awful. I would also have expected to have the possibility for a bulk update. Especially for archiving old versions one would expect to have the possibility to select versions "older than X" and archive them in a bulk change.

    Background: We migrated our issues from another system to JIRA and are now facing hundreds of versions which appear rather unsorted in the list.

  23. Anonymous

    Hello! I am trying a migration from JIRA 4.X to a newer version (5.X or 6.X). On the actual version I have integrated confluence 3.X. My question is: Would my confluence version be compatible with the newer version of JIRA? I mean, I don't want to improve my confluence too... Thank you!

  24. How to move Test cases from version 1 to version 2 with in the same project