This page is maintained for older versions of Spira only. The latest documentation can be found at:

SpiraTest Administration Guide Help Viewer

1. Introduction
2. Installing SpiraTeam®
3. System Administration
4. Appendices
1. Introduction
2. Installing SpiraTeam®
3. System Administration
4. Appendices

3.3. Custom Properties

SpiraTeam allows you to customize all of the artifacts in the system (requirements, test cases, incidents, etc.) by adding user-defined custom properties in addition to the built-in fields. You can create a variety of different types of custom properties. This section describes how you setup different custom lists and custom properties in your projects.

Artifacts in SpiraTeam can have up to 30 different custom properties per artifact-type, per project. There are different types of custom properties allowed:

  • Text: Normal or Rich-Text field.
  • Integer: Whole-Number entry.
  • Decimal: Fractional number entry (currency, etc.)
  • Boolean: Simple yes/no (on/off) checkbox.
  • Date: Date selector.
  • List: Custom List selector.
  • Multi-List: Custom List selector that allows multiple values.
  • User: List of assignable users.

Each custom property can have optional settings applied to it. Optional settings are as follows. (Note that not all settings are allowed for all property types.)

  • Default: The default value when a new artifact is created.
  • Allow Empty: Whether or not an empty value is allowed.
  • Precision: (Decimal Only) How many decimal places is allowed (or the value is rounded to).
  • Minimum Value: The minimum value allowed.
  • Maximum Value: The maximum value allowed.
  • Minimum Length: The minimum length of the data required in the field.
  • Maximum Length: The maximum length of the data allowed in the field.
  • Rich Text: Whether or not the text field allows HTML or not.
  • Custom List: The defined Custom List for the field that users can select from.

Important: Note that setting ‘Allow Empty’ to No will override any workflow step definitions, and will always require a value to be entered in, even if the workflow is configured to have the field disabled!