2		Getting Started with Gemini 5	usage items templates
2.5.6		Documents	admin usage
2.5.7		Standard Reports	usage reporting
2.5.8		The Calendar	usage items add-ons time plugins ms-outlook
3.1		Creating Tasks	items templates
3.2		Rapid Planning (Creating Multiple Tasks)	usage items templates
3.3		The View Item Page	usage items sentry
4		Structuring Projects	admin
4.1		Creating Projects	admin
4.2		Components in Gemini	admin
4.3		Versions in Gemini	admin
4.4		Setting Project Defaults	admin
7		Project Templates	admin templates
7.1		Project Templates: Introduction	admin templates
7.2		Project Templates: Process	admin templates
7.3		Project Templates: Screens and Visibility	admin templates
7.4		Project Templates: Process Workflow	admin templates
7.5		Project Templates: Custom Fields	admin custom-fields templates
7.6		Project Templates: Menus	admin templates
7.7		Project Templates: Status, Priority and Severity	admin templates
7.8		Project Templates: Resolution	admin templates
7.9		Project Templates: Links	admin templates
7.10		Project Templates: Time	admin templates
10.4		Projects
10.4.1		Project Concepts
10.4.1.1		Grouping Projects
10.4.1.2		Components
10.4.1.3		Versions
10.4.1.4		Roadmap
10.4.1.5		Change Log
10.4.1.6		Dashboard
10.4.2		Project Customization
10.4.2.1		Project Settings
10.4.2.2		Single, Multiple Item Options
10.4.2.3		Item Type, Priority, Severity Options
10.4.2.4		Default Values
10.4.2.5		Components
10.4.2.6		Versions
10.4.2.7		Project Attributes
10.4.2.8		Which Fields Are Displayed?	custom-fields
10.5.16		Patterns	usage items
10.12.12		Projects API	api

42 documents found.

Gemini uses the concept of Versions to help define iterations of a given project. Each iteration will usually consist of work items that need to completed within the iteration.  In software development speak, these iterations can represent software releases such such 1.0, 1.1, 2.0, etc.  If non-software projects are being managed with Gemini then the Versions may well represent more time centric labelling such as June, July, August, etc.

A key feature of versions in Gemini is the ability to nest them, arrange them in an hierarchical fashion.

Creating

The Version Number field is usually an internal value that means something to you but is not displayed in Gemini to end users.

The Version Name field is key and is used and displayed everywhere in Gemini. For example you could put “3.0”, “Phase 1” or “July”.

The Version Description field allows for a more detailed description to be captured.

The Version Parent option enables a version to be nested below another version.

Version Release

The Version Released option determines whether the given version has been completed / marked as released.

A released version will be visible on the project’s Road Map, whereas an unreleased version will be visible on the project’s Change Log.

Version Dates

The Version Start Date is optional and defines on which day work starts on the version.

The Version Release Date is optional and defines on which day work ends on the version.

Populating these dates will ensure that the Version Burndown Chart renders correctly (especially important for Scrum/Agile based projects).

Version Attributes

Every project can define additional meta data that can be attached to versions. These version attribute can hold additional information specific to each version that can be displayed to end users.

Every version attribute requires a Name and a Default Value.  For example you could add a “Release Notes” attribute that contained custom release notes per version.

Editing

Simply point and click any column to change the data within.

The Archived option hides a version from view and cannot be seen by users.

Clicking on the edit icon in the Actions column enables the creation and editing of version specific Milestones and Attributes.

Version Attributes

Project Administrators should first define any required version attributes and then set values for those attributes per version.

Version Milestones

Each version within a project can have it’s own milestones. These are subsequently displayed on the Version Burndown Chart.