Defects: Traceability Link Direction is Incorrect

[Jeff_Senley]

Defects are normally either standalone items or are downstream references from test runs where a test run has been executed and a defect has occurred during that execution.  The traceability browser reflects these in reverse, as the defect appears upstream from the test run which is logically incorrect.

We believe this error should be corrected; how are other life science companies addressing this?

[Catalina]

Hi @Jeff_Senley,

Thank you for your question!

It appears that your post has not yet received any response. I am replying to raise awareness. Hopefully, another community member will be able to help.

Also, feel free to add any additional information you think might be relevant. It sometimes helps to have screenshots to better understand what you are trying to do.

Best regards,

[VolkerEckardt · Accepted solution]

You are referring to this, Jeff?

[Jeff_Senley]

As previously noted, a defect is either a standalone item or a downstream item from some other artifact type.  I am not sure how the diagram above represents any difference in the existing system.

[VolkerEckardt]

Before I try to answer in more detail, can you please tell me how this affects your business processes, I mean, what is impossible for you because it points in the "wrong" direction?

[GeoffreyClemm]

The direction you are seeing is just the out-of-the box reference direction.   If you would like the reference to be in the other direction, remove the referencing field from the test run item (that links to a bug item), and add a referencing field to the bug item (that points to the test run item).

Note that the only semantic difference in codebeamer of the direction you pick is which item will hold the reference (which is the item which will get a new version when you change the reference).