This topic describes how to work with both system-defined fields and user-defined fields (UDFs). This includes creating user-defined fields (UDFs), and changing field display labels.
UDFs can be defined for shared spaces and workspaces. This overview describes how to work with shared and non-shared UDFs.
UDFs cannot be defined at the space level when the space is isolated.
Instead, admins for a workspace can define UDFs in individual workspaces.
The UDFs are available in that individual workspace only.
Shared spaces (Enterprise Edition)
This table summarizes the actions admins can perform when defining UDFs in shared spaces and associated workspaces.
|Shared space||Associated workspaces|
The space admin can add and modify UDFs defined in the shared space.
The UDFs are available to all associated workspaces.
Must UDF names and labels be unique?
If a UDF is defined for a shared space, you cannot create a UDF, or define a label, with the same name in the associated workspaces:
If a UDF is defined for an individual workspace, you cannot create a UDF, or define a label, with the same name in the associated shared space. You can create a UDF, or define a label, with the same name in other workspaces.
In Settings , click Spaces and select the shared space or the workspace where you want to create user-defined fields.
Click the Entities tab.
In the Entities list on the left side of the pane, select the item (such as user story, manual test, epic, and so on) for which you want to create your own fields.
Click the Fields tab.
Click + to add a user-defined field.
Enter the following:
Name Description Name
A unique name that APIs will use to access this field. No uppercase letters or punctuation allowed.
ALM Octane automatically adds the suffix _udf to the name of the field.
Label A unique name for the field as you want it displayed in the UI. You can enter English, non-English, and special characters. Field type
Select the field type from the drop-down.
Description Enter a description for the user-defined field.
Limitations: UDFs can only be defined in English even if ALM Octane has been localized for a specific language.Limits on the number of UDFs you can define per workspace
Field type Maximum no. of UDFs allowed per workspace
String and Boolean
A total of 100 between the two types.
Note: String fields can contain up to 255 characters.
Number 50 Date and time 20 List Unlimited User Unlimited Release Unlimited Team Unlimited Long string
Note: Long string fields can contain up to 1500 characters.
Note: You can modify this value by setting the MEMO_UDFS_LIMIT configuration parameter MEMO_UDFS_LIMIT.
If you are adding a user-defined field of list type:
Select the list to use for the field.
For details on creating your own lists, see Set up lists.
If you want the user-defined field to select multiple value, check the Allow multiple values check box.
If you are adding a user-defined field of user, release, or team type, select the reference field on which to base the new field's value.
To add the user-defined field to existing forms, select the forms from the Add to form drop-down list.
UDFs are available in ALM Octane like other predefined system fields.
You can set attributes for the user-defined field, such as making the field mandatory, by creating rules for entity types. For details, see Set up rules.
If a user-defined field is Required, but the default Smart View form for adding an item does not display the new user-defined field, ALM Octane still prompts you for a value in the Other Required and Invalid Fields section. This section displays only when needed.
If a user-defined field (UDF) is no longer relevant, you can delete it.
In your entity, select the user-defined field in the grid, and in the toolbar, click the Delete button X.
The deleted field is handled accordingly:
|Entity Forms||Fields are cleared from a form the next time the form is opened.|
|Rules||A warning is displayed. All rules containing the field are invalid and deactivated.|
The field is no longer available as an option. Additionally,
Group By filters
Fields in filters are cleared with a message. Reset the filters (either in the grid or in the dashboard configuration) as needed.
|Sorting order||The field is cleared from the sorting with a message.|
|Grid displays||The field is removed from the grid display without a message.|
|Favorites||Fields in a favorite are cleared without a message.|
In addition, the name of the field remains in the server audit log.
You can change the display names of both UDFs and system fields.
Tip: ALM Octane also lets you change display labels for entities. For details, see Customize entity display labels (Enterprise Edition).
To change field labels:
In Settings , click Spaces and select a shared space or workspace.
Click Entities > Fields, and select a field.
Modify the Label field and click Save.
Some grids list multiple entities in a combined view. To display correctly, the field labels for all the entities have to match.
|Backlog grid||Includes defects, user stories, and quality stories.|
Includes manual tests, Gherkin tests, test suites, and automated tests.
|Run grid||Includes manual test runs and automated test runs for test suites.|
Solution: In Settings, change the label for the field for all relevant entities.
Defects, quality stories, and user stories have an Author field.
You want to change the label from Author to Creator.
In Settings, modify the Author field label to Creator three times, once for each of the three entities separately: Defects, quality stories, and user stories.
The combined Backlog grid in ALM Octane displays the Creator label correctly.
Limitation: If a field is not available for all entities in the combined grid, ALM Octane does not display the new label.