Upstream requirement version is not linked to traceability report

[Vinoth_V]

Hello Team,

If we try to generate traceability between SRS and SGD, the generated report links the downstream requirement to the upstream requirement, but without mentioning the version of the covered upstream requirement.

Which means that if an SRS requirement was changed and its version is incremented, the traceability will not detect this change and the downstream SGD requirement will still appear to cover the SRS requirement, although it has been changed and the version attribute has changed.

So, if the traceability report links the downstream requirement to the version of the covered upstream requirement, any change in the upstream requirement will be detected.

[EvaBertalan]

Hi @Vinoth_V ,

The reference between upstream and downstream items are independent on the version of the items by default.

If your workflow requires to refer to a specific version, you can use versioned reference by setting this on the field containing the upstream reference:

With this setting the reference will be marked with the version of the upstream reference.

Version number will be the current one at the time when the relation has been created.

If you set the Propagation too, the upstream reference will be marked if there were any change on the item.

[Vinoth_V]

Hello @EvaBertalan 

Could you please provide me with the steps to reach the configuration options found in the screenshot you provided?
Thanks in advance.

[EvaBertalan]

Hi @Vinoth_V ,

These are the steps:

• open a tracker, which has a reference field to another tracker (in my case: User Stories)
• open the more menu, marked with three dots in the header
• select Configure
• go to Fields tab
• click on the label of the reference field (in my case: Epic)
• you will see the dialogue I've shared