1		Installing Gemini 5
1.1		Pre-requisite Checks
1.2		Installing Gemini 5 Using Automated Installer
1.3		Installing Gemini 5 Using Zip File
1.4		Upgrading 5.0 to 5.1
1.5		Upgrading 4.2 to 5.1
1.6		Using Windows Authentication
1.7		Setting up with Geckoboard
1.8		Setting up with Lucidchart
1.9		MS Project Connector
2		Getting Started with Gemini 5
2.1		Signing in to Gemini
2.2		Navigation in Gemini
2.3		AppNav Cards
2.4		Gemini Terminology
2.5		Features and Functions
2.5.1		The Grid
2.5.2		The Planner
2.5.3		Activity Page
2.5.4		Timeline Page
2.5.5		Roadmaps and Changelogs
2.5.6		Documents
2.5.7		Standard Reports
2.5.8		The Calendar
2.5.9		Burndown and Burnup Charts
2.5.10		Ad Hoc Reporting with Excel
2.5.11		The Data Import Wizard
3		Creating and Managing Tasks
3.1		Creating Tasks
3.2		Rapid Planning (Creating Multiple Tasks)
3.3		The View Item Page
4		Structuring Projects
4.1		Creating Projects
4.2		Components in Gemini
4.3		Versions in Gemini
4.4		Setting Project Defaults
5		Breeze - Email-to-ticketing
5.1		Introduction to Breeze
5.2		Breeze: Queues
5.3		Breeze: SMTP Servers
5.4		Breeze: Mailboxes
5.5		Breeze: Response Templates
6		Sentry - Testing in Gemini
6.1		Introduction to Sentry
6.2		Test Cases
6.3		Test Plans
6.4		Test Runner (Executing Tests)
6.5		Test Run History
7		Project Templates
7.1		Project Templates: Introduction
7.2		Project Templates: Process
7.3		Project Templates: Screens and Visibility
7.4		Project Templates: Process Workflow
7.5		Project Templates: Custom Fields
7.6		Project Templates: Menus
7.7		Project Templates: Status, Priority and Severity
7.8		Project Templates: Resolution
7.9		Project Templates: Links
7.10		Project Templates: Time
8		People and Permissions
8.1		Users
8.2		Groups
8.3		Permissions
8.4		Active Directory Integration and Windows Authentication
9		Code Review & Source Control Connectors
9.1		SVN Server Installation
9.2		Client Side Gemini Tortoise SVN Integration
9.3		Git Source Control Connector
9.4		Mercurial Source Control Connector
9.5		TFS Source Control Connector
9.6		Using Saucery for Code Review
10		Gemini 4
10.1		Getting Started
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
10.3		Upgrading
10.3.1		Upgrading Existing Installations
10.3.2		Upgrading 4.1.x to 4.2
10.3.3		Upgrading 4.0.x to 4.2
10.3.4		Upgrading 3.7.x to 4.2
10.3.5		Upgrading 3.6.x to 4.2
10.3.6		Upgrading 3.5.x to 4.2
10.3.7		Upgrading 3.1.x to 4.2
10.3.8		Upgrading 3.0.x to 4.2
10.3.9		Upgrading 3.0.0 to 4.2
10.3.10		Upgrading 2.2 to 4.2
10.3.11		Upgrading 2.1.x to 4.2
10.3.12		Upgrading 2.0.x to 4.2
10.3.13		Upgrading 1.9.1 to 4.2
10.3.14		Upgrading 1.9/1.9a/1.9b to 4.2
10.3.15		Upgrading 1.8.x to 4.2
10.3.16		Upgrading 1.7 to 4.2
10.3.17		Upgrading 1.6.3 to 4.2
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?
10.5		Item Management
10.5.1		Overview
10.5.2		Creating
10.5.3		Editing
10.5.4		Viewing
10.5.5		Visibility
10.5.6		Custom Fields
10.5.7		Comments
10.5.8		Hierarchy
10.5.9		Links
10.5.10		Recurrence
10.5.11		Estimates & Time Logs
10.5.12		Source Control Links
10.5.13		Audit Trails
10.5.14		Workflow
10.5.15		Filter Items
10.5.15.1		Using the Filter
10.5.15.2		Saving and Reusing Filters
10.5.15.3		Cross Project Roll-ups
10.5.16		Patterns
10.6		Planning Board
10.7		Time Management
10.7.1		Time Reports
10.7.2		Recording Time
10.8		Notifications
10.8.1		Project Alerts
10.8.2		Item Watchers
10.9		Test Management
10.9.1		Approach
10.9.2		Plans
10.9.3		Cases
10.9.4		Runs
10.9.5		Traceability
10.9.6		Filtering
10.10		Management
10.10.1		Administration
10.10.1.1		General Configuration
10.10.1.2		SMTP and Notifications
10.10.1.3		Projects
10.10.1.4		Custom Fields
10.10.1.5		Item Management
10.10.1.6		Test Management
10.10.1.7		Licensing
10.10.2		Users & Security
10.10.2.1		User Management
10.10.2.2		Global and Project Groups
10.10.2.3		Working with Global Groups
10.10.2.4		Working with Project Groups
10.10.2.5		Available Permissions
10.10.2.6		Project Resources
10.10.2.7		Assigning Permissions to Projects
10.10.2.8		Windows Authentication
10.10.2.9		Active Directory Integration
10.11		Using Add-on Products
10.11.1		Visual Studio 2008/2010
10.11.2		Gemini Desktop
10.11.3		Microsoft Outlook
10.11.4		Converse
10.11.4.1		Installation
10.11.4.2		Core Mailbox Setup
10.11.4.3		Selecting Emails to Process
10.11.4.4		Manipulating Email Content
10.11.4.5		Outbound Notifications
10.11.4.6		Project Mapping
10.12		API
10.12.1		Introduction
10.12.2		Enabling API support
10.12.3		Authentication
10.12.4		Response Formats
10.12.5		.NET Quick-start
10.12.6		Schema Reference
10.12.7		Administration API
10.12.8		Alerts API
10.12.9		Custom Fields API
10.12.10		Groups API
10.12.11		Items API
10.12.12		Projects API
10.12.13		Users API
10.12.14		Testing API
10.13		User Profile

194 documents found.

Project Templates

The terms ‘Process’ and ‘Type’ are synonymous in Gemini. A Type is type of transaction and different types of transactions may have different attributes. For example, in a Template related to Software Development, a “Change Request” may require different fields, security and workflow from a “Bug”. The Change Request might require an Approver, which Bug might not. Similarly, Bug might require that the Browser Version be captured, which is not relevant to Change Request. The workflow for these two type is also likely to be different – the Change Request might have the following: Requested…Approved…In Progress…Tested…Closed, while Bug might have Logged…Under Investigation…In Development…in QA etc. Of course the workflow is unlikely to be quite so linear, so there is complexity to defining these different types of process even though they might be handled by the same people. Consider that  the situation could arise where only a QA Lead is allowed to change the status of Bug to complete and only the PM can change the statuses on Change Request. These types of requirements exist in every department all of the time and Gemini takes care of them with ease.

Since each ’type’ of transaction can have completely different values and workflow, each type of transaction is a process, hence the use of the term in Gemini. Below is an explanation of how you can create and manage a ‘Process’.

Navigate to the Customization section from the Customize link in the top right hand section of the menu. If you have the appropriate privileges you will then be able to navigate to the Templates tab and the Process sub tab (see below).

To add a new Process click on the Add button. You will be prompted to provide:

• A label by which your process will be know
• An icon to represent your process (we deliver dozens of icons for you to choose from or you can create your own)
• A colour code so that when using Gemini (the Visual Planner especially) you can easily distinguish between transactions/tasks for different processes.

Click Save to create the Process

To maintain the label of the Process, you click in the field and use Gemini’s inline editing to easily and instantly change the value. To delete a Process click on the Delete icon to the right of the screen. Orphaned tasks are not allowed, so if you delete a Process you must supply a different Process for all tasks that might belong to the deleted process to be moved to.

Once you have created the Process definition you need to decide which data fields you need for data capture around the process and who is allowed to see and interact with those fields. For more information on this see:

Project Templates: Screens and Visibility

Project Templates: Status, Priority and Severity

Project Templates: Custom Fields

Once you have defined the metadata that your Process requires, you will need to define the Workflow that your Process will follow. To define Workflow, you must first have defined the Statuses that items in your Process might pass through eg. “Open”, “Assigned”, “Closed” etc. as you will be defining how your items move from status to status. For information on how to do this see:

Project Templates: Process Workflow