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

8 documents found.

An item in Gemini represents something that can be assigned to a resource (or resources) that requires effort to complete it. An item can represent a Bug, Task, Enhancement, Requirement, Change Report, Support Ticket, Investigation or anything you wish. Gemini allows for different meta data to be attached to items even in different projects with full control over the definition of item associated meta-data. The following represents a typical view of an item and it’s associated meta data:

Such customizations can only be performed by Gemini Administrators. Here are the full customization options at the item level.

General Options

The Time in Working Day option represents the hours:minutes in your typical working day.

You can also choose between rich text editing or plain text for Item Descriptions and Item Comments.

The Item Link Qualifier is used to automatically turn text such as “GEM:995” into a hyperlink to the item itself (e.g. GEM:995).

The Show Images option can be used to show/hide item type, priority, severity and status images such as follows:

Item Types

Gemini Administrators can introduce their own Item Types with relevant imagery.

Every Item in Gemini must have an Item Type (e.g. Bug, Enhancement, Task).

Item Types can be organized into groups that can subsequently be allocated to different projects.

This ensures that only relevant, applicable meta-data is applied to each project – this is what Countersoft terms “Relevant Project Experience”.

Furthermore, every Item Type can have it’s own Screen definitions that determine who sees what field and when. Furthermore, an Item Type can also have it’s own workflow (that overrides the containing Project’s workflow).

Item Priority

Gemini Administrators can introduce their own Item Priority with relevant imagery.

Every Item in Gemini can have an Item Priority (e.g. Low, Medium, High) that determines when an Item should be scheduled/addressed.

Item Priority values can be organized into groups that can subsequently be allocated to different projects.

Item Severity

Gemini Administrators can introduce their own Item Priority with relevant imagery.

Every Item in Gemini can have an Item Severity (e.g. Trivial, Minor, Major) that determines the actual impact of an Item.

Item Severity values can be organized into groups that can subsequently be allocated to different projects.

Item Status & Workflow

Typically an Item will transition from “creation” to “closure” during it’s life-time.  Those transitions are represented by Item Status values that an Item may flow through. For example, a Task may flow as follows:

• Unassigned
• Assigned
• In Progress
• Closed

The following default Item Status values ship with Gemini which Gemini Administrators can customize as required.

Once you have defined the potential list of Item Status values, assemble them into an Item Workflow that can be attached to either a Project or an Item Type.

Essentially, you define which Item Status values can participate in the workflow and then edit each one and set it’s transitions as required.

Note how you can select the outbound transitions AND specify who user groups can set them.

Item Resolution

An Item’s Resolution determines it’s final outcome. Did we fix it? Was it duplicate request? Did we put it on hold?

Resolution values apply across all projects.

Item Link Types

Every Item can be linked to another – not in terms of workflow – but in terms of referential information such as “these two items are duplicates”.

Gemini Administrators can define customize Link Types with appropriate descriptions.

Item Time Types

Users can specify the type of time they are logging. Define your own time types to help gain better insight into the type of work being performed by project resources.

Item Screens

A Bug can have a different input fields from a Change Request. Furthermore, the Bug editing experience can be different from when raising a new Bug.

You can define different screens for creating, viewing, editing and even commenting stage. First define your screen:

Now edit the screen and select who can see which fields – including Custom Fields.

Once defined, simply attach the screen definition to the appropriate stage: