Global Fields allow account owners to define and manage fields at the account level and make them available across multiple projects. They help maintain consistent field structures and values across projects while reducing duplication and manual configuration.
Supported Field Types
Global Fields support the following custom field types:
- List
- Multi List
- Linked List
Managing Global Fields (Account Level)
Global Fields are managed from Account Settings and are available only to Account Owners.
Accessing Global Fields
- Go to Account Settings
- Open the Global Fields tab
Creating a Global Field
From the Global Fields tab, account owners can create a new field by clicking on the ‘Create New Field‘ button. Once inside the new field screen, you can define:
- Field Name
- Field Format (List, Multi List, or Linked List)
- Field Values:
- Add new values
- Reorder values
- Delete values
Editing Global Fields
Account owners can update Global Fields at any time. Changes are automatically reflected in all linked projects.
Supported updates include:
- Renaming the field
- Adding new values
- Reordering values
- Deleting values – simply hover the value you wish to delete and click on the delete icon
Note: Deleting a value that is already used across projects will remove it from all relevant projects, leaving affected fields empty. Any linked values will also be deleted.
Using Global Fields in Projects (Project Level)
While Global Fields are created at the account level, they are configured per project.
Linking Global Fields to a Project
- Go to Project Settings
- Open the Fields tab
- Scroll to the Custom Fields section
Global Fields will appear at the bottom of the custom fields list with the global icon next it their name. Click on the pencil icon to edit and link in to entities.
From here, users with the appropriate permissions can:
- Link Entities: Choose which entities will include the Global Field:
- Requirements
- Tests
- Test Sets
- Issues
- Milestones
- Set Default Values: Define a default value that will be pre-filled when a new entity is created.
- Set as a Mandatory Field (Per Entity): Decide whether the field is required for each linked entity type.
Once entities are linked, the Global Field becomes available in that project.
Please Note: Project-level users cannot edit the field name, change the field type, add/delete values, or delete the entire Global Field. All of those changes are controlled centrally from Account Settings.
Migrating Project Fields to Global Fields
The Migration Tool allows you to consolidate existing project-level custom fields into a single Global Field, helping you standardize structure across projects and reduce duplication.
To access the Migration Tool:
- Go to Account Settings.
- Open the Global Fields tab.
- Click the Migration Tool button in the top-right corner.
This will open a dedicated migration screen where you can begin the process.
Step 1: Select Fields to Migrate
In the first step, you define which project-level fields will be replaced by a Global Field.
- Select Global Field: Choose the Global Field that will become the main field, replacing the selected project-level fields.
- Select Project-Level Fields: Choose the custom fields you want to replace with the selected Global Field. You can select fields from different projects, but only one field per project.
For example, you can replace the “Operating System” custom field in three different projects with a single “OS” Global Field.
In the Available Fields section, you will see all eligible project-level fields, including the project name in parentheses. You can narrow down the list by typing part of the field name.
Note: Fields that are mapped for integrations cannot be replaced using the Migration Tool.
To select a field, click the “+” icon next to it. The field will move to the Selected Fields section on the right.
Once you have selected all relevant fields, click ‘Continue to Step 2’ to proceed.
Step 2: Map Field Values
In this step, you map existing project-level field values to the values of the selected Global Field. This ensures consistency and prevents duplication of similar values across projects.
On the left side of the screen you’ll see all project field values. On the left side you’ll see the mapping to the global field values.
- If a project-level value has an exact match with a Global Field value, the system will automatically map them. These values will be highlighted with a blue “G” indicator.
Note: Exact matching is case-sensitive.
- If there is no exact match, the project-level value will appear with a green “P” indicator. Leaving it as is will add this value to the Global Field.
If you prefer to map it to an existing Global Field value instead, click the value and select an existing option or create a new one.
If you do not want to manually map values and prefer to add all project-level values directly to the Global Field as new values, simply tick the checkbox above the grid.
After completing the mapping, click on ’Continue to Confirmation’.
Migration Confirmation
Before completing the migration, the system will display a confirmation message explaining:
- The selected Global Field will replace the chosen project-level fields.
- Dashboards and reports using the project-level fields will automatically update to use the Global Field.
- The number of entities that will be affected and updated with the new Global Field and its values.
Click ‘Approve’ to complete the migration.