Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

You'll find everything about using the Team Versions app on this page. From creating versions to shipping releases.


About the Versions Manager

You can create and manage versions from the Team Versions manager, accessible from the project navigation or the apps menu on Jira’s main navigation.

When you open the Team Versions app, you'll first see a list of the versions available in your Jira instance. If there aren’t any versions, you can create the first one [link to create version].

 

Team Versions app home screen:

List of versions available in all the projects of your Jira instance.

  1. Search field: filter the versions list to find the right one quickly.

  2. Reload: update the versions list with the latest changes.

  3. Create version

  4. Detailed list of versions: status, progress, start & end date, description, and actions.


Managing Versions

Create Version

You can easily create a version in the Team Versions manager:

Instructions:

  • Click the “Create version” button.

  • Type the name for the version.
    [new version modal]

  • [Optional] Add a start and end date.

  • [Optional] Add a description.

  • Click the “Save” button.

You can also create versions directly in an issue [link to create in an issue].


Edit Version

You can edit the details of any Unreleased and Archived versions at any moment.

Instructions:

  • In the versions list, find the one you want to edit and click the context menu.

  • Click the “Edit” option.

  • Edit the fields as needed.

  • Click “Save.”

You can also edit the version on the detail page [link to detail page].


Release Version

You can release a version anytime by clicking the “Release” button in the versions list.

A confirmation dialog opens:

  • ✅ If all issues are done, you can confirm the release date and press “Release.”

  • ⚠️ If there are unresolved issues, you can move them to a different version or ignore them, confirm the release date, and press “Release.”

You can also release the version on the detail page [link to detail page].

Unrelease Version

If needed, you can revert a release. On the versions list, open the context menu and click the “Unrelease” option.


Archive Version

It’s possible to archive versions you won’t need but want to keep a record. From the versions list, open the context menu and click the “Archive” option.

Unarchive Version

Plans might change, and you can unarchive a version by opening the context menu and clicking the “Unarchive” option.


Delete Version

If you no longer need a version, you can delete it. From the versions list, open the context menu and click the “Delete” option.

A confirmation dialog opens:

  • ✅ If the version has no associated issues, you can confirm by pressing “Delete.”

  • ⚠️ If the version has associated issues, you can move them to a different version or remove the version information from the issues and confirm by pressing “Delete.”

” button.

You can add multiple issues at once.

Moving issues to a different Version



 

This action is undoable.



Version detail vision

Versions have a detail view.

  • view issues attached to the version

  • add issues

  • move issues to a different version

  • release

 

Version detail page

When the user clicks the version name, a detail page opens.

 

The name, dates and description fields are editable inline. If the user enters a version name already in use, the name doesn’t update and a flag appears.

~~~~~~~~

 

Issues section:

The issues section includes a progress bar of the version that reflects the done / in progress / to do issues.

The issues are organized in a table, that can be filtered with the tabs.

 

Users can add issues to the version, either from the empty view or the add issues button in the issues section. Multiple issues can be added at a time. 

 



  • No labels