2		Getting Started with Gemini 5	items projects templates
2.1		Signing in to Gemini	admin
2.2		Navigation in Gemini
2.3		AppNav Cards
2.4		Gemini Terminology
2.5		Features and Functions
2.5.1		The Grid	items Excel
2.5.2		The Planner	items
2.5.3		Activity Page	items time
2.5.4		Timeline Page	items time
2.5.5		Roadmaps and Changelogs	items time
2.5.6		Documents	admin projects
2.5.7		Standard Reports	projects reporting
2.5.8		The Calendar	items projects add-ons time plugins ms-outlook
2.5.9		Burndown and Burnup Charts	items time reporting
3		Creating and Managing Tasks	items
3.2		Rapid Planning (Creating Multiple Tasks)	items projects templates
3.3		The View Item Page	items projects sentry
6.1		Introduction to Sentry	items testing sentry
6.2		Test Cases	items testing sentry
6.3		Test Plans	items testing sentry
6.4		Test Runner (Executing Tests)	items testing sentry
6.5		Test Run History	items testing sentry
9.6		Using Saucery for Code Review	saucery
10		Gemini 4
10.1		Getting Started	install
10.5.16		Patterns	projects items
10.6		Planning Board
10.7.2		Recording Time	items
10.8		Notifications	emails
10.8.1		Project Alerts	emails
10.8.2		Item Watchers	emails
10.11		Using Add-on Products	add-ons
10.11.1		Visual Studio 2008/2010	add-ons visual-studio
10.11.2		Gemini Desktop	add-ons desktop
10.11.3		Microsoft Outlook	admin add-ons ms-outlook
10.13		User Profile

37 documents found.

The View Item page is one of the most important pages in Gemini. It is where you can see the full details of a task and access some significant task management functionality, both through the options on the page and the Content controls, which are in effect widgets with application logic behind them.

Understanding the View Item Page

Attributes

One easy way to understand the View Item page is to break it into two sections. On the left hand side of the page are what Gemini refers to as “Attributes”. These are the fields that are defined for the Project Template. Classic Attributes are fields like “Status”, “Priority” and “Severity”. To access these fields simply click on them and Gemini’s Inline Editing is available to you, to allow you to change their values instantly and effortlessly. Inline Editing will take you straight to the field that you clicked on but will also allow you to edit all of the other Attributes at the same time. Click Save to commit your changes.

Fig 1.0 Attributes such as “Status” etc are shown on the left hand side of the View Item page.

Content

The middle of the View Item page is known as the Content Area and the fields displayed here are referred to as Content. This distinction becomes clearer if one looks at Screens as part of the Process configuration of the Customization section. In Screens, you choose the fields for your processes(and visibility settings to apply)  when Creating, Editing or Viewing an Item. Below this section is a list of what can be fields or apps (widgets) in the Content area.

An easy way to understand ‘content’ in Gemini is to consider it as “data with logic”. For example, Comments in Gemini exist in the Content section of Screens under Viewing. This is because in Gemini, when you add a comment, you can choose which groups can see that comment; so there is application logic behind the field. The same is true of say Dependencies, because there is logic to allow users to add and remove dependencies in that part of the Content area. So Dependencies, like Comments are sophisticated functionality, not simple fields.

Fig 2.0 Content such as “Comments” etc are shown in the middle of the View Item page.

Why does Gemini have the distinction between Attributes and Content?

Some of the objects classed as Content represent full-blown apps. For example the entire functionality for Sentry, the Testing application that is fully integrated into Gemini, is deployed into Gemini using Content apps.

Because of this flexible, plug-in framework, you can extend and integrate Gemini in an almost endless variety of ways. Users can have widgets that connect to 3rd party CRM systems, diagramming software, extended document stores etc and all within the baseline framework of Gemini. Extensibility through Widgets is easy to implement because Gemini and its sister products are built in exactly that way and there is no more robust solution than an application that is built using its own features and framework.

Functional Controls on the View Item Page

The functionality that is specific to the process of managing a specific item is placed on the View Item page. This includes the ability to:

• Move a Task from one project to another
• Edit a Task
• Delete a Task

Fig 3.0 View Item Control

When moving a Task, Gemini will prompt with a list of projects that you have access to. When you select a different project from the one that the Task resides in, you will also be able to access all of the destination project’s fields, including Process. In this way it is possible to say move a ‘Ticket’ from a Help Desk project into a bug-tracking project as a ‘Bug’, or a task that reflects ‘Requirements’ in one project to a ‘Software Development Task’ in another. It is also possible to keep all of the Processes you need in a single project and implement any separation needed through permissions; with Gemini, the choice is yours.