2		Getting Started with Gemini 5	projects templates
2.5.1		The Grid	Excel
2.5.2		The Planner
2.5.3		Activity Page	time
2.5.4		Timeline Page	time
2.5.5		Roadmaps and Changelogs	time
2.5.8		The Calendar	projects add-ons time plugins ms-outlook
2.5.9		Burndown and Burnup Charts	time reporting
3		Creating and Managing Tasks
3.2		Rapid Planning (Creating Multiple Tasks)	projects templates
3.3		The View Item Page	projects sentry
6.1		Introduction to Sentry	testing sentry
6.2		Test Cases	testing sentry
6.3		Test Plans	testing sentry
6.4		Test Runner (Executing Tests)	testing sentry
6.5		Test Run History	testing sentry
10.5.16		Patterns	projects
10.7.2		Recording Time

18 documents found.

Gemini uses Versions to help define iterations within a given project. Each iteration will usually consist of tasks that need to completed within the iteration.  In software development speak, these iterations can represent software releases such as “1.0”, “1.1”, “2.0” etc.  If non-software projects are being managed with Gemini then the Versions may well represent more time centric labelling such as June, July, August, etc.

Not all projects will require or make use of Versions to clearly define which work items will take place and when. However, as a general rule of thumb, if you can break down a project into phases then you can use Versions to track those phases.

A key feature of Versions in Gemini is the ability to nest them in hierarchical fashion.  If a project does not require iterations to be tracked then Versions need not be defined and can be removed from view using the Project Template Process Screens.

For more on Versions and how to create, maintain and apply them, see the document “Versions in Gemini”.

The Roadmap lists every item, by Version, where the Version that it has been assigned to is not marked as “Released”. Once a Version is marked as “Released” that Version and the items in it appear on the Changelog. In this way the Roadmap can be said to embody work yet to be done, a current/future release or phase.

The Changelog represents work that has been done, at least in so far as it occurred within the specified iteration that a Released Version covered.

To place a task on the Roadmap or Changelog you must select the appropriate Version in the “Affected Version” field when creating or editing the task. If you wish to use Roadmap and Changelog functionality you must therefore enable this field on Process Screens in your Project Template(s).

Access to the Roadmap or Changelog is determined by the Project Template Menu definition and as with all other menus, the Roadmap and Changelog menus can be renamed to more accurately fit with the terminology of the group who will use this functionality.

Functionality in the Roadmap & Changelog

The Roadmap and Changelog both provide summary views of the items within their scope (see screenshot at the end of this document).

Inline Editing of values

Right mouse click on any item in a Roadmap or Changelog and Gemini will popup an Inline Editing Control to let you:

• View  - Open the item in the View Item page
• Comment  - Add a comment (with the ability to specify comment visibility)
• Edit  - Change item values immediately
• Pin/Un-Pin- Create an AppNav Card to the item)
• Follow/Un-Follow  - Add yourself to a list of people to receive email notifications on changes to the item
• Delete - Delete the item if you have permissions to do so and this does not break data integrity rules.

The Roadmap and Changelog Header Layout

Fig 1.0 Description of the key elements on the Roadmap and Changelog screens