| Keywords: |
|
|
Gemini Community Support Site
This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities. |
42 documents found.
Versions in Gemini
Versions in Gemini define iterations of a given project. Each iteration will usually consist of tasks that need to completed within the iteration. In software development these iterations might represent software releases such such “1.0”, “1.1”, “2.0” etc. If non-software projects are being managed with Gemini then Versions may well represent more time-centric values such as “June”,”July”, “Q1”,”Q2” etc.
A key feature of Versions in Gemini is the ability to nest them in a hierarchical fashion. Thus you can create Versions like:
Fig 1.0 3 different examples of Versions in Gemini
To make your Versions even more logical within the context of your organization, Gemini lets you rename the Version field (as it does all other fields) so you could label Version “Sprint” or “Fiscal Period” or “Release” in your Project Template to match the examples listed above. And because Gemini lets you have multiple Project Templates, you could have all three variants for the different teams in your organization.
To create Versions, navigate to the project for which you wish to create values and select “Settings” from the project menu. You will then see the following options just below the menu bar. Click on Versions.
| Fig 2.0 Versions in Gemini as they are in the baseline | Fig 2.1 Versions in Gemini (renamed as “Budget Period”) |
If you change Versions to something else in your Project Template, for example to “Budget Period” (as illustrated above) you will see your terminology in the Project Settings option.
To Add a new Version, click on the Add button and you will be prompted to provide:
- Version Name
- Description
Click Save to create the Version. This is all that you need to do to create a Version though you may wish to add more information as outlined below.
When you have created your Versions you can, if you wish, build a Version hierarchy. There are two ways to do this:
- Click in the “Parent” column and select the parent Version of the Version you have created from the list of Versions
- Drag and drop your Version wherever it belongs using the “Sequence and Indent” control on the extreme right of the page.
Fig 3.0 Drag-drop sequencing control
The other fields to maintain against Versions are:
*Start Date – when the Version starts.
*Release Date – when the Version is planned to end.
*These two dates determine the range of a Burndown Chart on the selected Version.
Archived - hides a version from view so it cannot be seen by users
Released – If Released, a version will be visible on the project’s Changelog, whereas an unreleased version will be visible on the project’s Roadmap (see Roadmaps and Changelogs).
To maintain any of the Version’s field values, click in the appropriate field and use Gemini’s inline editing to easily and instantly change the field value.
To delete a Version click on the Delete icon to the right of the screen. You will be asked to confirm the deletion. Deleting a Version removes it from the system and clears the “Fixed in Version” value against all tasks associated with the Version, effectively removing them from Version visibility (Roadmap, Changelog, Burndown and Burnup charts).