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 10 Next »

Create and manage your Versions.


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.

On this page, you'll find everything about using the Team Versions app. From creating versions to shipping releases.

When you open the Team Versions app, the first thing you'll see is a list of the versions available in your Jira instance. If there aren’t any versions yet, 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

  2. Reload the versions list

  3. Create version

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

Search Versions

It’s possible to type on the search field to filter the versions list so you can quickly find the right one.

Reload the Versions list

Use the reload button to update the list with the latest changes.

Create Version

The user can create new versions, as seen previously, from the empty screen and then from a button on the top right side of the app.


Managing versions

Release Version

Archive Version

Delete Version

Version detail vision

Versions have a detail view.

  • view issues attached to the version

  • add issues

  • move issues to a different version

  • release

Version operations

Creating a new version

It’s possible to create a new version from:

  • the app page (full-screen and with sidebar alike);

  • the issue by clicking the new version button.

The name for the version is mandatory, and the field has focus on when the user opens the modal. The new version will then be available in all projects and will show in the app.

The save button is disabled until the user enters a name. Dates and descriptions are optional.


Release version

Users can release versions at any moment by clicking the “release” button.

If everything is done, the modal displays a confirmation modal to confirm the release date.

 

If there are unresolved issues, the user must send them to a different version or ignore them.

When the user releases a version, a flag appears to confirm the status change.


Unrelease version

Previously released versions can be unreleased from the [···] menu. A flag appears to confirm the status change.


Edit version

When the user edits a version, a flag appears to confirm the status change.


Archive / Unarchive version

Toast message to confirm the status change


Delete version

A user can delete version a version from the table.

A confirmation dialog is shown if the version has associated issues. The user can choose to move issues to a different version or just delete the version.

If the version has no issues, it’s deleted directly, and a toast is shown.



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