Report and track product defects

This topic describes how to submit and manage defects in ALM Octane.

Report defects

You can submit defects at all stages of your work.

Work area How
Backlog module

In any of the backlog grids, select + > Defect.

The new defect is associated with the feature selected in the tree.

Quality module

In the Defects tab, create a new defect.

The new defect is associated with the application module selected in the tree.

Inside a story or test (after the test ran)

In the Details tab of a user story, quality story, or test, click the Report Defect button .

ALM Octane associates the defect with the current item's feature.

During a manual test run

Click and then Add new defect.

In the Tests tab of a pipeline's latest run

In the Pipelines module, open the pipeline run and select the Tests tab.

  1. Select one or more automated test runs.

  2. Click Report Defect.

ALM Octane links the new defect to the selected runs and contains a link to the Tests page of the relevant pipeline run.

Back to top

Track and analyze defects

Watch defects like any Backlog item:

  • Add filters to view relevant defects.

  • Track defect progress in the Dashboard Module or the Overview tab.

  • Connect defects with features, user stories, or application modules.

Back to top

Copy a defect to a different workspace

You can copy defects from one workspace to another.

Copying a defect to another workspace is useful, for example, if you are dependent on users in other workspaces to handle parts of your defect. You can create a defect for the other users in their workspace, and then verify the fixes before closing the defect in your workspace.

You can only copy to a different workspace if: 

  • You have access to it.

  • It is associated with the same shared space as the workspace with the original defect.

How to copy a defect to another workspace:

  1. For the defect, click Copy to Different Workspace.

  2. Choose the target workspace and click Copy.

  3. Click the link in the message to open the new defect in the other workspace.

The new defect created with the same name as the original defect, in the New phase. The Detected By is the user who copied the original defect.

A comment is automatically added that contains a link to the workspace of the original defect. If you have access, click the link to open the original defect.

What is copied?
  • Common fields.

    This varies depending on the entities that the workspaces share.

    Example: If the release of the original defect is defined at the shared space level, the value is copied. If the release of the original defect is defined at the workspace level, the release is not available in the other workspace and is not copied.

  • User-defined fields (UDFs) that are defined at the shared space level and are common to both workspaces

  • Attachments

  • Tasks

What is not copied?
  • Comments

  • History

  • Test runs and old versions

Back to top

See also: