Report and track product defects
This topic describes how to submit and manage defects in ALM Octane.
You can submit defects at all stages of your work.
In any of the backlog grids, select + > Defect.
The new defect is associated with the feature selected in the tree.
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 Test Defects and then Add new defect . If there are no defects assigned to this run, clicking Test Defects opens the Add Run Defect dialog box. For details, see Report defects during a run.
|In the Tests tab of a pipeline's latest run||
In the Pipelines module, open the pipeline run and select the Tests tab.
ALM Octane links the new defect to the selected runs and contains a link to the Tests page of the relevant pipeline run.
Watch defects like any Backlog item:
Track defect progress using widgets in the Dashboard module or the Overview tab.
In the Relations tab, link defects to user stories, requirements, test runs or other defects.
- Also in the Relations tab, link defects to their covering tests. The defects are then listed in the tests' Backlog Coverage field.
You can track the quality of your fixed defects by analyzing the status of the tests covering the defects.
One test can cover many defects, and one defect can be covered by many tests.
To define test coverage of a defect, do one of the following:
- In the Relations tab of a defect, link the defect to its covering test.
- In the Relations tab of a test, link the test to its covered defect.
The covered defect is listed in the test's Backlog Coverage field.
The covering tests are listed in the defect's Test Coverage field. The field represents the tests that cover a defect, grouped by their various statuses.
Tip: You can filter defects according to whether or not they have covering tests:
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:
For the defect, click Copy to Different Workspace.
Choose the target workspace and click Copy.
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?||
|What is not copied?||
You can move defects from one workspace to another.
You can only move to a different workspace if:
You have the Move defect permission on both workspaces.
It is associated with the same shared space. You cannot move defects between workspaces in isolated spaces.
You can only move one defect at a time.
|What is moved?||
|What is not moved?||
Note: The defect in the target workspace might not be valid due to the removal of fields that are irrelevant in the target workspace. In such a case, any user attempting to modify the defect will be required to adjust it to make it valid.
To move a defect to another workspace:
- In the defect Details tab, click Move to Different Workspace.
In the Move to Different Workspace dialog box, select the target workspace, and then click Move.
Refresh the grid in the target workspace to view the change.