On the ALM sidebar, select Defects.

• You can add user-defined fields and change the label of any of the fields in the Defects module. You can also customize project lists. For details, see the ALM help: Customize project entities and Customize field lists.

• You can use the Script Editor to restrict and dynamically change the fields and values in the Defects module. For details, see Create and edit workflow scripts using Script Editor.

• When you select a defects column with a user name value (including user-defined fields), ALM displays a list with the name and full name of each user. You can search for users, sort users, group users by user group, and select users from the users list or a group tree. For user interface details, see Work with users list.

Work with defects in ALM

The actual number of days needed to fix the defect. If this field is left blank, ALM automatically calculates the Actual Fix Time as Closing Date–Detected on Date.

The user name of the person who is assigned to fix the defect.

The application version in which the defect was closed.

The date on which the defect was closed.

Comments about the defect. To add a new comment, click the Add Comment button. A new section is added to the Comments box, displaying your user name and the database's current date.

A unique numeric ID for the defect, assigned automatically by ALM. The Defect ID is read-only.

Describes the defect in detail.

The user name of the person who submitted the defect.

The cycle in which the defect was detected.

When assigning a defect to a cycle in the Detected in Cycle field, ALM automatically assigns its release to the Detected in Release field.

The release in which the defect was detected.

The application version in which the defect was detected.

The date on which the defect was detected.

Default: The current database server date.

The environment on which the defect was detected. Environments are a combination of operating systems, browsers, and so on, on which you test the application.

The estimated number of days required for fixing the defect.

The date and time when this defect was last changed.

The version in which the defect is planned to be fixed.

The priority of the defect, ranging from low priority (level 1) to urgent priority (level 5).

The name of the project where the defect occurs.

Whether the defect can be recreated under the same conditions by which it was detected.

Default: Y

The severity of the defect, ranging from low (level 1) to urgent (level 5).

The current status of the defect. Defect status can be one of the following: Closed, Fixed, New, Open, Rejected, Reopen.

Default: New

The subject folder.

A brief summary of the defect.

The cycle in which the defect is targeted to be fixed.

When assigning a defect to a cycle in the Target Cycle field, ALM automatically assigns its release to the Target Release field.

The release in which the defect is targeted to be closed.