Opening the Team Versions Manager:
Team Versions will be accessible from:
the apps menu in the main navigation;
from the project sidebar;
Populated table
With builds available, the list is populated in a table with the following:
Version
Status
Progress
Start date
End date
Description
Actions (Release, more options: Edit, Unrelease, Archive / Unarchive, Delete)
It’s possible to type on the search field to filter the versions and click the “All statuses” dropdown to filter the specific status of releases.
What can be done with versions
Users can perform various operations:
create / edit / archive / unarchive / release / unrelease / delete
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.
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
…
...
...
...
Issue view
User flows
Team Versions will be accessible from:
the issue view as a custom field.
Adding a version to an issue:
Team Versions is available as a custom field in the issue details.
When the user clicks the field, the field is focused, and a dropdown shows up.
The user can select one or more versions from the list. It’s also possible to start typing to filter the list. The dropdown has several sections that can be omitted if they’re empty:
recent versions
unreleased versions
released versions
--- divider ---
create version
When a version is added to the input field, it has a [x] button that lets the user remove it. It also has a clear button on the right side.
Clicking outside the dropdown closes it, and the input field is no longer selected, and the clear options are hidden.
The user can click the version name to open the version detail page (details below).
Adding a version to an issue (fallback)
If it’s not possible to implement the flow with a dropdown directly in the custom field, the fallback is a pop-up with the dropdown to select the versions and the option to create a new version.
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.
~~~~~~~~~~~~~~~
📐 Confirmation flag: [Version name] createdhttps://www.figma.com/file/3rWq3ENHwXlWzPYD0YW75g/Team-Versions?node-id=57%3A14751&t=HPWMofr12NlFfRPP-4
📐 Error: This version name already exists https://www.figma.com/file/3rWq3ENHwXlWzPYD0YW75g/Team-Versions?node-id=57%3A15330&t=HPWMofr12NlFfRPP-4
...
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.
📐 Mocks - all done: https://www.figma.com/file/3rWq3ENHwXlWzPYD0YW75g/Team-Versions?node-id=76%3A23888&t=ljqwydm5x7PKzOqP-4
If there are unresolved issues, the user must send them to a different version or ignore them.
📐 Mocks - warnings: https://www.figma.com/file/3rWq3ENHwXlWzPYD0YW75g/Team-Versions?node-id=76%3A21860&t=ljqwydm5x7PKzOqP-4
~~~~~~~~~~~~
When the user releases a version, a flag appears to confirm the status change.
📐 Confirmation flag: [Version name] released https://www.figma.com/file/3rWq3ENHwXlWzPYD0YW75g/Team-Versions?node-id=57%3A15942&t=HPWMofr12NlFfRPP-4
...
Unrelease version
Previously released versions can be unreleased from the [···] menu. A flag appears to confirm the status change.
📐 Mocks - toast: https://www.figma.com/file/3rWq3ENHwXlWzPYD0YW75g/Team-Versions?node-id=57%3A15942&t=HPWMofr12NlFfRPP-4
...
Edit version
📐 Mocks - Edit: https://www.figma.com/file/3rWq3ENHwXlWzPYD0YW75g/Team-Versions?node-id=58%3A16625&t=HPWMofr12NlFfRPP-4(similar to create modal)
~~~~~~~~~
When the user edits a version, a flag appears to confirm the status change.
📐 Confirmation flag: [Version name] updated https://www.figma.com/file/3rWq3ENHwXlWzPYD0YW75g/Team-Versions?node-id=58%3A16055&t=HPWMofr12NlFfRPP-4
...
Archive / Unarchive version
Toast message to confirm the status change
📐 Confirmation flag: [Version name] archived https://www.figma.com/file/3rWq3ENHwXlWzPYD0YW75g/Team-Versions?node-id=58%3A17057&t=HPWMofr12NlFfRPP-4
📐 Confirmation flag: [Version name] un archived https://www.figma.com/file/3rWq3ENHwXlWzPYD0YW75g/Team-Versions?node-id=58%3A17451&t=HPWMofr12NlFfRPP-4
...
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 de version.
If the version as no issues, it’s deleted directly, and a toast is shown.
📐 Mocks - delete: https://www.figma.com/file/3rWq3ENHwXlWzPYD0YW75g/Team-Versions?node-id=58%3A18240&t=ljqwydm5x7PKzOqP-4
📐 Confirmation flag: [Version name] deleted https://www.figma.com/file/3rWq3ENHwXlWzPYD0YW75g/Team-Versions?node-id=58%3A17846&t=HPWMofr12NlFfRPP-4
...
Version detail
When the user clicks the version name, a detail page opens.
📐 Mocks - Version detail: https://www.figma.com/file/3rWq3ENHwXlWzPYD0YW75g/Team-Versions?node-id=33%3A9571&t=ljqwydm5x7PKzOqP-4
📐 Mocks - Version detail - options expanded: https://www.figma.com/file/3rWq3ENHwXlWzPYD0YW75g/Team-Versions?node-id=74%3A19703&t=ljqwydm5x7PKzOqP-4
📐 Mocks - Version detail - empty view https://www.figma.com/file/3rWq3ENHwXlWzPYD0YW75g/Team-Versions?node-id=74%3A20897&t=ljqwydm5x7PKzOqP-4
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.
~~~~~~~~
📐 Edit name: https://www.figma.com/file/3rWq3ENHwXlWzPYD0YW75g/Team-Versions?node-id=74%3A22896&t=ljqwydm5x7PKzOqP-4
📐 Error: A version with this name already exists https://www.figma.com/file/3rWq3ENHwXlWzPYD0YW75g/Team-Versions?node-id=74%3A23193&t=ljqwydm5x7PKzOqP-4
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.
📐 Add issues: https://www.figma.com/file/3rWq3ENHwXlWzPYD0YW75g/Team-Versions?node-id=74%3A21361&t=ljqwydm5x7PKzOqP-4
📐 Confirmation flag: [Issue key] added / [number] issues added https://www.figma.com/file/3rWq3ENHwXlWzPYD0YW75g/Team-Versions?node-id=74%3A22491&t=ljqwydm5x7PKzOqP-4
Issue operations flags
📐 Confirmation flag: [Issue key] moved to [version name] https://www.figma.com/file/3rWq3ENHwXlWzPYD0YW75g/Team-Versions?node-id=74%3A20106&t=ljqwydm5x7PKzOqP-4
📐 Confirmation flag: [Issue key] removed from this version https://www.figma.com/file/3rWq3ENHwXlWzPYD0YW75g/Team-Versions?node-id=74%3A20502&t=ljqwydm5x7PKzOqP-4
...
Future developments
Admin settings
Select projects that can use Team Versions
Select users that can create / manage / release versions
Team Files integration
attach files and folders to version details
new automation: create a folder and attach it to the version page
Automations:
Do things when a version is published