2		Getting Started with Gemini 5	usage items projects
2.5.11		The Data Import Wizard	admin items database Excel migration
3.1		Creating Tasks	items projects
3.2		Rapid Planning (Creating Multiple Tasks)	usage items projects
7		Project Templates	admin projects
7.1		Project Templates: Introduction	admin projects
7.2		Project Templates: Process	admin projects
7.3		Project Templates: Screens and Visibility	admin projects
7.4		Project Templates: Process Workflow	admin projects
7.5		Project Templates: Custom Fields	admin projects custom-fields
7.6		Project Templates: Menus	admin projects
7.7		Project Templates: Status, Priority and Severity	admin projects
7.8		Project Templates: Resolution	admin projects
7.9		Project Templates: Links	admin projects
7.10		Project Templates: Time	admin projects

15 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