Creating requirement attribute data types

You can create custom attribute data types that can be used in custom attributes. Attribute data types define the properties of the attribute values. They provide structure and consistency to custom attributes by offering the administrator a limited set of data types that have a predefined behavior and constraints.

Before you begin

You must have administrator permissions to create and modify attribute data types.

About this task

Custom attribute data types are available for use in all custom and non-custom attributes in the project. New custom attribute data types must be based on one of three kinds:
  • Simple
  • Enumerated list of values
  • Bounded range of values
Simple data types use one of the following base data types:
An integer.
A number that can contain decimal digits.
A check box (marked or cleared).
A calendar entry.
A 24-hour time selection or an entry in this format: hours:minutes:seconds.
Calendar and time entries.
Alphanumeric text.
A time duration entry (integers) in hours, days, or weeks.
Search the repository team members and select one.
An enumerated list of values is a numbered list of values with textual labels. You can add and remove numbered entries and arrange entries in any order.
Tip: If a data type uses an enumerated list of values, note the order of the values in the table. That order is the same order that the values will be in when you assign the attribute value to any artifact; for example, in the artifact sidebar. The number that is assigned in the value field is the number that is used when artifacts are sorted by that attribute. When you order artifacts by an attribute (ascending), the enumerations with the lowest value will be first.
For a bounded range of values, you must specify a minimum and maximum for a range of any of the following base data types:
An integer.
A number that can contain decimal digits.
A calendar entry.
Calendar and time entries.


To create a custom attribute data type:

  1. Click the Administration menu Administration menu item, and then click Manage Project Properties.
    Note: If configuration management is enabled for your project, on the Administration menu, click Manage Component Properties.
    An administrative page opens that has tabs for artifact types, attributes, data types, link types, and templates.
  2. Click the Attribute Data Types tab.
  3. Click New Data Type.
  4. Enter a name and description for the data type.
  5. Select a kind of value and a base data type, where applicable.
  6. If you plan to work with an enumerated list or a bounded range of values, create entries as needed.
  7. Optional: In the URI field, specify a unique URI to identify the attribute data type across RM projects.

    Within a project, you must use a unique URI for each attribute data type. If another project has an equivalent data type, you should use the equivalent type's URI to ensure consistency across projects and enable a shared vocabulary for reporting. In a project that is enabled for configuration management, you can use the same URI for equivalent attribute data types that are in different components.

    For example, Project_A has an attribute named "Glossary_visibility", which has an enumerated list of values: Enterprise, Organization, or Project, each corresponding to an integer. When you create Project_B, you define an attribute named "Definition_scope". Possible values are Corporation, Division, and Team. Your organization considers these data types equivalent even though their names and enumeration values differ. Assign the same URI to both data types to ensure consistent meaning across projects and so that you can report on equivalent data types across projects.

  8. Click Save.
  9. To edit enumeration label, select the Attribute Data Type that has its Base Data Type as enumerated on the left side.
  10. Select the label that you want to edit, enter a name, and then click Save.
    Note: You cannot edit the enumeration label of the pre-defined attribute data type.