Skip to main content
雨
雨高_146008564-Participant
4-Participant
June 2, 2026
Solved

Issues with automatic tracing of test cases

  • June 2, 2026
  • 3 replies
  • 58 views

I am using Codebeamer Release 2.2.1.3 . On Tracker, there is an issue: test cases are auto-traced to system requirements, but we don’t want automatic tracing when the verification method is design review.Automatic tracing of test cases to system requirements shall be omitted, provided that the verification method is specified on the system requirement and the method is design review. The compute code is as below:

    Best answer by BKampling_SAI

    Try wrapping the existing logic in a conditional that returns null when the verification method is Design Review:

    yourCustomFieldPropertyNameForVerificationMethod is NOT "Design Review" ? distinct(downstreamReferences(this).trackerTypes("testcase").{item|item.customField[5]} != ""
          ? downstreamReferences(this).trackerTypes("testcase").{item|item.customField[5]} : null)
      : null

    An important note, choice fields in Codebeamer behave as collections even when single-select, so you usually can't compare them to a string directly — you compare against the option name, e.g. something like !this.customField[N].name.contains("Design Review") or by the option ID, depending on how that field is set up. That's the one piece worth testing carefully.

    Also, after editing the formula, add Verification Method to the field's Compute dependencies so the TestCaseID value recomputes whenever the verification method changes.

    3 replies

    雨
    雨高_146008564-ParticipantAuthor
    4-Participant
    June 2, 2026

    distinct(downstreamReferences(this).trackerTypes("testcase").{item|item.customField[5]} != "" ? downstreamReferences(this).trackerTypes("testcase").{item|item.customField[5]}: null)////////compute code///I think you should add precondition that the verification of the requirement is design review can not be auto traced by test case

    BKampling_SAI
    BKampling_SAI13-Aquamarine
    13-Aquamarine
    June 3, 2026

    The tracing will always be present between two linked items, regardless of status. You can configure a traceability report to exclude items of a specific status if this is a reporting issue. Could you provide more context around what you are trying to accomplish?

    雨
    雨高_146008564-ParticipantAuthor
    4-Participant
    June 4, 2026

    Thanks for your reply.But it is not a reporting issue. The auto-trace rule is set by codebeamer system. And the compute rule lose a condition.There is a one situation that  i do not want the system  requirement auto-traced by test case because the software requirement is traced by artificial retrospective tracing.(software requirement is downstream of system  requirement).The situation is when the verification method of system  requirement is design review

     

    BKampling_SAI
    BKampling_SAI13-AquamarineAnswer
    13-Aquamarine
    June 5, 2026

    Try wrapping the existing logic in a conditional that returns null when the verification method is Design Review:

    yourCustomFieldPropertyNameForVerificationMethod is NOT "Design Review" ? distinct(downstreamReferences(this).trackerTypes("testcase").{item|item.customField[5]} != ""
          ? downstreamReferences(this).trackerTypes("testcase").{item|item.customField[5]} : null)
      : null

    An important note, choice fields in Codebeamer behave as collections even when single-select, so you usually can't compare them to a string directly — you compare against the option name, e.g. something like !this.customField[N].name.contains("Design Review") or by the option ID, depending on how that field is set up. That's the one piece worth testing carefully.

    Also, after editing the formula, add Verification Method to the field's Compute dependencies so the TestCaseID value recomputes whenever the verification method changes.

      Terms & ConditionsAccessibility statement