Associating two requirements

Anthony C.

What methods does everyone use to tie two requirements together aside from using the Relate function?

The following comes to mind, but just want to check with everyone else:

1. Using Tags
2. Having a field attribute to the requirement. This attribute would be a custom field that is Item of Type.

Alessandro Valli

you can misuse links and use the hyperlink of the other item. Links get not versioned and you can not filter for a specific link (advanced filter)

Anthony C.

@Alessandro Valli Thank you for your suggestion.

Did you intend to state "…you can use links…"?

In regard to the statement of links not getting versioned, I don't think I clearly understand. Did you mean that once I take a link for an item at Version 1, the link will always take me to Version 1, even thought the requirement is at Version 2? I experimented with this and found that the link does take me to the most current version.

Lastly, that's a good point you made about not easily filtering on the URL content.

Alessandro Valli

Links are not fields, thus do not generate a new item version in case of change (you have special fields for URL if I remember correctly … never used, BTW).

There is kind of versioning for relationships now (it is the reason why you can also see relationship changes in the baseline comparison report, e.g.).

You can add the url of an item in a link of another item, but the solutuion is not maintenable. If an item gets deleted the relationship is gone, but the link has a dead end …