Custom Fields on References

Depending on your specific circumstances, Dan, I think you can get most of the way there with the where clause support for referenced items. Check out section 5.1.1 in the custom reports guide (Reports / Custom Reports on the ribbon bar) for details, but if you were to have three custom fields on your requirements - replaces, extends and includes - and put the appropriate requirement references in there, you could use something like the following to get the references you're looking for:

$listReferencedRequirements where RefLocation = Replaces

In addition to a where clause for the release you're reporting (e.g., $repeatRequirements where Release = 1.3), I think that should be about right. Give that a shot, and let us know how it works for your goals.

Thanks for the note. This is a good idea, and I ended up doing something similar. The problem is really the many-to-many relationship disappears. A single requirement may replace multiple requirements, etc., and this approach will only allow for a 1-to-1 relationship.

Would be a nice feature to have.

Hm. You say that, "...this approach will only allow for a 1-to-1 relationship." Did you know you could put multiple requirements into the custom fields, so that you could report on more than just a single "replaced" element?

Ok, but how would I iterate through them? I am showing comments like this:
New Requirement: Details
Original Requirements: Details (could be more than 1)

Hey Dan, I'm unable to attach files here in the forum, so I've created a follow-up support ticket to this on your behalf. Let's take the conversation over there. :-)