Relate items to other items

Relate items to each other for coverage and to see how one item impacts others. The Relations tab of any ALM Octane item displays a graphical representation these relations.

ALM Octane creates some relations automatically, such as the links between a test and its runs.

Relate items

  1. In any ALM Octane item, click the Relations tab.

    ALM Octane displays a graphical representation of all items linked to the current item.

    If several items of the same type are related to the current item, ALM Octane groups these items:

  2. In the toolbar, click Add Relation and select the type of item to which you want to link.

  3. Select the items from the displayed list, and click Select.

Back to top

Examples

Tests
  • In the Backlog module, relate a test to a user story or a feature for tracking coverage.

  • Report defects while running a test. If you create the defects while using the Manual Runner, defects are related to the test.

  • View the relationship between a test and test suites to which it is linked.

Test Suites
  • Relate a user story or feature to a test suite.

  • View relationships between a test suite and other items. To view a list of related tests, go to the Tests tab.

Runs

  • Relate defects to a run, even if you didn't report them during the run.

  • When you run a test, its corresponding test run is related to the test.

Defects
  • In the Quality module, relate a defect to an automated test.

  • Relate defects to each other.

Back to top

Types of relations

Inside ALM Octane, each type of item has specific relations to other item:

Entity Relation Descriptions
Requirements
  • Requirement (Trace to). A requirement created as a result of this requirement.

  • Requirement (Trace From). A requirement that necessitated the opening of this feature.

  • Linked feature: A feature linked to this requirement.

  • Linked defect. A defect related to this requirement.

  • Linked manual test: A manual test included in the requirement's tests.

  • Linked test suite: A test suite included in the requirement's tests.

  • Linked Gherkin test: A Gherkin test included in the requirement's test.

  • Linked automated test: An automated test included in the requirement's tests.

Epic
  • Epic (Trace to): An epic created as a result of this epic.

  • Epic (Trace from): An epic that necessitated the opening of this epic.

Feature
  • Covering Manual Test/Gherkin Test: A test covering the functionality of this feature.

  • Covering Automated Test: An automated test that tests the functionality of this feature.

  • Covering Test Suite: A test suite that tests the functionality of this feature.

  • Feature (Trace to): A feature created as a result of this feature.

  • Original Feature (Trace from): A feature that necessitated the opening of this feature.

  • Covering requirement: The requirement associated with this feature.

User story/quality story
  • Linked Defect: A defect related to this user story.

  • Covering Manual Test/Gherkin Test: A test that tests the functionality of this user story.

  • Covering Automated Test: An automated test that tests the functionality of this user story.

  • Covering Test Suite: A test suite that tests the functionality of this user story.

  • User Story (Trace to): A user story created as a result of this user story.

  • User Story (Trace from): a user story that necessitated the opening of this user story.

Defects
  • Linked User Story: A user story affected by this defect.

  • Linked Manual Run: A manual test run during which someone reported this defect.

  • Linked Automated Run: An automated test run during which someone reported this defect.

  • Linked Gherkin Auto Run: an automated Gherkin run during which someone reported this defect.

  • Linked Suite Run: A suite run during which someone reported this defect.

  • Defect (Trace to): A defect created as a result of this defect.

  • Defect (Trace from): A defect that necessitated the opening of this defect.

  • Linked requirement: A requirement to which the defect is attached.

Manual Tests
Gherkin Tests
Test Suites
  • Covered user story: A user story that this test (suite) covers.

  • Covered feature: A feature that this test (suite) covers.

  • Covering automated test: An automated test connected with this test that has the same general steps as the test.

  • Covered requirement: The requirement associated with this test.

Manual run
Automated run
Linked defect: A defect discovered during this manual run.
Automated test
  • Covered user story: A user story that this automated test covers.

  • Covered feature: a feature that this automated test covers.

  • Covering automated test: An automated test connected with this test that has the same general steps as the test.

  • Covered requirement: The requirement associated with this test.


Manual run
Suite run
Automated run

Linked defect: A defect created during this run.