1		Installing Gemini 5	admin migration
1.1		Pre-requisite Checks	admin
1.2		Installing Gemini 5 Using Automated Installer	admin
1.3		Installing Gemini 5 Using Zip File	admin
1.4		Upgrading 5.0 to 5.1	admin migration
1.6		Using Windows Authentication	admin security
1.8		Setting up with Lucidchart
9.3		Git Source Control Connector	add-ons source-control
9.4		Mercurial Source Control Connector	add-ons source-control
9.5		TFS Source Control Connector	add-ons source-control
10.1		Getting Started	usage
10.2		Installing
10.2.1		Requirements
10.2.2		Automated Installer
10.2.3		Microsoft Web Platform
10.2.4		Zip File
10.2.5		Scheduler Service	emails
10.3		Upgrading	migration
10.3.1		Upgrading Existing Installations	migration
10.3.2		Upgrading 4.1.x to 4.2	migration
10.3.3		Upgrading 4.0.x to 4.2	migration
10.3.4		Upgrading 3.7.x to 4.2	migration
10.3.5		Upgrading 3.6.x to 4.2	migration
10.3.6		Upgrading 3.5.x to 4.2	migration
10.3.7		Upgrading 3.1.x to 4.2	migration
10.3.8		Upgrading 3.0.x to 4.2	migration
10.3.9		Upgrading 3.0.0 to 4.2	migration
10.3.10		Upgrading 2.2 to 4.2	migration
10.3.11		Upgrading 2.1.x to 4.2	migration
10.3.12		Upgrading 2.0.x to 4.2	migration
10.3.13		Upgrading 1.9.1 to 4.2	migration
10.3.14		Upgrading 1.9/1.9a/1.9b to 4.2	migration
10.3.15		Upgrading 1.8.x to 4.2	migration
10.3.16		Upgrading 1.7 to 4.2	migration
10.3.17		Upgrading 1.6.3 to 4.2	migration
10.10.1.7		Licensing	admin
10.12.2		Enabling API support	api

37 documents found.

Previous releases of Gemini instances can be upgraded to the lates release whilst ensuring your project data remains intact after migration.

Download Gemini Web Application ZIP file. The automated installer should not be used.

You should remember to backup any custom images that you may have added as you will need to re-deploy them after migration.

Remember that you must always use the latest "web.config" file.

SQL Server 2000

Gemini 4.0 will be last release that will support SQL Server 2000. You should use any stored procedures labelled as "SQL2000". Certain data column types will also require manual script changes.

Migration from 1.x or 2.x Release

Legacy release installations can also migrate to their instances to the latest release. However the following caveats should be noted:

• Data that breaks database integrity will not be migrated and the migration scripts will call out such anomalies.
• User permissions will need to re-applied due the differing user permission models.

During the migration process existing data tables will remain intact and all data will be moved into new data tables (e.g. "issues" data goes into "gemini_issues").

Note the following new concepts/changes that the latest generation of Gemini brings:

• User Groups - global and at the project level
• Permissions - defined globaly and then applied to projects
• Custom Fields - defined globally and then "attached" to projects that require them. Use the Move facility to merge duplicate custom fields.
• Item Type - new types and icons introduced. Ability to vary this meta-data by project.
• Item Priority - new types and icons introduced. Ability to vary this meta-data by project. Priority tells you when something should be done.
• Item Severity - new types and icons introduced. Ability to vary this meta-data by project. Severity tells you what is the impact.
• Item Status & Workflows - new workflow steps and transition approach. Workflow can be applied to a project as well as individual item types.
• Screens - define who sees which fields and when. have separate screens for when creating and editing.
• Default Values - specify per project data default values. Useful when you need to hide input fields from users.
• Item & Comment Visibility - previous Private/Public switch replaced with the ability to show certain items or comments to selected user group.