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?

17 documents found.

Components are used to break down a project into smaller logical areas thereby ensuring Bugs, Tasks, Support Tickets end up in the right "part” of  a project.

Components can be nested to provide a hierarchical representation of your project. 

Components can also be used to define “sub-projects” within a project.

Creating Components

Creating components is simply a case of typing in component details.

Component Name should be short and succulent in order to quickly convey the area of the project represented by the component.

Component Description enables a more detailed description to be captured that is displayed in various locations within Gemini to help users understand the component.

Component Lead is optional and identifies the person responsible for the component.

Component Parent is optional and is used to organize components in a hierarchical fashion.

Editing Components

Simply point click and inline edit any element of a component.

The Locked option ensures that no more items can be assigned to that component.

Sort & Order

You can drag-drop the ID column of any component to re-order components.