1		Installing Gemini 5	install migration
1.1		Pre-requisite Checks	install
1.2		Installing Gemini 5 Using Automated Installer	install
1.3		Installing Gemini 5 Using Zip File	install
1.4		Upgrading 5.0 to 5.1	install migration
1.5		Upgrading 4.2 to 5.1	migration
1.6		Using Windows Authentication	install security
2.1		Signing in to Gemini	usage
2.5.6		Documents	usage projects
2.5.11		The Data Import Wizard	items database templates Excel migration
4		Structuring Projects	projects
4.1		Creating Projects	projects
4.2		Components in Gemini	projects
4.3		Versions in Gemini	projects
4.4		Setting Project Defaults	projects
7		Project Templates	projects templates
7.1		Project Templates: Introduction	projects templates
7.2		Project Templates: Process	projects templates
7.3		Project Templates: Screens and Visibility	projects templates
7.4		Project Templates: Process Workflow	projects templates
7.5		Project Templates: Custom Fields	projects custom-fields templates
7.6		Project Templates: Menus	projects templates
7.7		Project Templates: Status, Priority and Severity	projects templates
7.8		Project Templates: Resolution	projects templates
7.9		Project Templates: Links	projects templates
7.10		Project Templates: Time	projects templates
8		People and Permissions	security
8.1		Users	security
8.2		Groups	security
8.3		Permissions	security
8.4		Active Directory Integration and Windows Authentication	security
10.10		Management
10.10.1		Administration
10.10.1.1		General Configuration
10.10.1.2		SMTP and Notifications	emails
10.10.1.3		Projects
10.10.1.4		Custom Fields
10.10.1.5		Item Management	items
10.10.1.6		Test Management	testing
10.10.1.7		Licensing	install
10.10.2		Users & Security	security
10.10.2.1		User Management	security
10.10.2.2		Global and Project Groups	security
10.10.2.3		Working with Global Groups	security
10.10.2.4		Working with Project Groups	security
10.10.2.5		Available Permissions	security
10.10.2.6		Project Resources	security
10.10.2.7		Assigning Permissions to Projects	security
10.10.2.8		Windows Authentication	security
10.10.2.9		Active Directory Integration	security
10.11.3		Microsoft Outlook	add-ons ms-outlook usage
10.12.7		Administration API	api

52 documents found.

To simplify data entry and improve data accuracy it is often advisable to set default data capture values for your projects.

Project Defaults are determined by the Processes that have been defined in the Project Template that your projects are created from and the fields on the Screens that they are set to use. If, for example, you have a project from a Template that uses the out-of-the-box field “Status” and a Custom Field “Browser Version” then you will be able to set defaults for both fields because Gemini treats Custom Fields as if they were part of the core application.At the same time, if you have two processes, “Bug” and “Task” and “Bug” uses Browser Version but Task does not, then you will be able to set the default value for “Browser Version” just for processes of type “Bug”. 

To setup Project Defaults,navigate to the project for which you wish to create values and select “Settings” from the project menu. You will then see the following options just below the menu bar. Click on Defaults.

Fig 1.0 Project Defaults in Gemini

You will be prompted to set defaults for all processes in your projects, or for a specific process. Setting defaults for a specific process will always override the settings for all processes.

Fig 2.0 Drop-down of “All” or specific process defaults

You will see every field from a superset of fields representing data capture screens from all of the possible processes in your project.

If you select a specific process then you are setting defaults for just that process but you will still see every field. This gives you two very important capabilities. The first is that you can capture data programmatically that is not shown on a screen, but which might be important for some integration with a non-Gemini system. The second, and more common scenario, is that you can easily transition your tasks not just from one status to another, but from one Process Type to another.

You could, for example, set up a type “Ticket”, which captures data from incoming support requests. At that stage the person capturing the data will not necessarily know about the process that subsequently occurs if an incoming issue turns out to be a bug in software that a development team will have to handle. If the Ticket turns out to represent a bug, then someone with the appropriate permissions could change its Process Type to “Bug” and rather than having all of the fields associated with a Bug being empty, the Ticket (now Bug) could have all of the correct defaults for the Software Development team to take over.

To create Project Defaults simply choose whether the default relates to “All” or a specific process, enter/select the values that you wish to act as defaults, and click Save.