10		Gemini 4	usage
10.1		Getting Started	install usage
10.2		Installing	install
10.2.1		Requirements	install
10.2.2		Automated Installer	install
10.2.3		Microsoft Web Platform	install
10.2.4		Zip File	install
10.2.5		Scheduler Service	install
10.3		Upgrading	install migration
10.3.1		Upgrading Existing Installations	install migration
10.3.2		Upgrading 4.1.x to 4.2	install migration
10.3.3		Upgrading 4.0.x to 4.2	install migration
10.3.4		Upgrading 3.7.x to 4.2	install migration
10.3.5		Upgrading 3.6.x to 4.2	install migration
10.3.6		Upgrading 3.5.x to 4.2	install migration
10.3.7		Upgrading 3.1.x to 4.2	install migration
10.3.8		Upgrading 3.0.x to 4.2	install migration
10.3.9		Upgrading 3.0.0 to 4.2	install migration
10.3.10		Upgrading 2.2 to 4.2	install migration
10.3.11		Upgrading 2.1.x to 4.2	install migration
10.3.12		Upgrading 2.0.x to 4.2	install migration
10.3.13		Upgrading 1.9.1 to 4.2	install migration
10.3.14		Upgrading 1.9/1.9a/1.9b to 4.2	install migration
10.3.15		Upgrading 1.8.x to 4.2	install migration
10.3.16		Upgrading 1.7 to 4.2	install migration
10.3.17		Upgrading 1.6.3 to 4.2	install migration
10.4		Projects	projects
10.4.1		Project Concepts	projects
10.4.1.1		Grouping Projects	projects
10.4.1.2		Components	projects
10.4.1.3		Versions	projects
10.4.1.4		Roadmap	projects
10.4.1.5		Change Log	projects
10.4.1.6		Dashboard	projects
10.4.2		Project Customization	projects
10.4.2.1		Project Settings	projects
10.4.2.2		Single, Multiple Item Options	projects
10.4.2.3		Item Type, Priority, Severity Options	projects
10.4.2.4		Default Values	projects
10.4.2.5		Components	projects
10.4.2.6		Versions	projects
10.4.2.7		Project Attributes	projects
10.4.2.8		Which Fields Are Displayed?	projects custom-fields
10.5		Item Management	items
10.5.1		Overview	items
10.5.2		Creating	items
10.5.3		Editing	items
10.5.4		Viewing	items
10.5.5		Visibility	items
10.5.6		Custom Fields	custom-fields items
10.5.7		Comments	items
10.5.8		Hierarchy	items
10.5.9		Links	items
10.5.10		Recurrence	items
10.5.11		Estimates & Time Logs	items time
10.5.12		Source Control Links	items
10.5.13		Audit Trails	items
10.5.14		Workflow	items
10.5.15		Filter Items	items find-filter
10.5.15.1		Using the Filter	items find-filter
10.5.15.2		Saving and Reusing Filters	items find-filter
10.5.15.3		Cross Project Roll-ups	items find-filter
10.5.16		Patterns	usage projects items
10.6		Planning Board	usage
10.7		Time Management	items time
10.7.1		Time Reports	items time
10.7.2		Recording Time	usage items
10.8		Notifications	usage
10.8.1		Project Alerts	usage
10.8.2		Item Watchers	usage
10.9		Test Management	testing
10.9.1		Approach	testing
10.9.2		Plans	testing
10.9.3		Cases	testing
10.9.4		Runs	testing
10.9.5		Traceability	testing
10.9.6		Filtering	testing
10.10		Management	admin
10.10.1		Administration	admin
10.10.1.1		General Configuration	admin
10.10.1.2		SMTP and Notifications	admin
10.10.1.3		Projects	admin
10.10.1.4		Custom Fields	admin
10.10.1.5		Item Management	admin items
10.10.1.6		Test Management	admin testing
10.10.1.7		Licensing	install admin
10.10.2		Users & Security	admin security
10.10.2.1		User Management	admin security
10.10.2.2		Global and Project Groups	admin security
10.10.2.3		Working with Global Groups	admin security
10.10.2.4		Working with Project Groups	admin security
10.10.2.5		Available Permissions	admin security
10.10.2.6		Project Resources	admin security
10.10.2.7		Assigning Permissions to Projects	security admin
10.10.2.8		Windows Authentication	security admin
10.10.2.9		Active Directory Integration	admin security
10.11		Using Add-on Products	usage add-ons
10.11.1		Visual Studio 2008/2010	usage add-ons visual-studio
10.11.2		Gemini Desktop	usage add-ons desktop
10.11.3		Microsoft Outlook	admin add-ons ms-outlook usage
10.11.4		Converse	converse
10.11.4.1		Installation	converse
10.11.4.2		Core Mailbox Setup	converse
10.11.4.3		Selecting Emails to Process	converse
10.11.4.4		Manipulating Email Content	converse
10.11.4.5		Outbound Notifications	converse
10.11.4.6		Project Mapping	converse
10.12		API	api
10.12.1		Introduction	api
10.12.2		Enabling API support	install api
10.12.3		Authentication	api
10.12.4		Response Formats	api
10.12.5		.NET Quick-start	api
10.12.6		Schema Reference	api
10.12.7		Administration API	admin api
10.12.8		Alerts API	api
10.12.9		Custom Fields API	custom-fields items api
10.12.10		Groups API	security api
10.12.11		Items API	items api
10.12.12		Projects API	projects api
10.12.13		Users API	security api
10.12.14		Testing API	testing api
10.13		User Profile	usage

123 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.