Thanks for the reply.

So what's the best practice? We placed the Requirements in a collection, and then did the review. Now we have to go and change the artifacts ourselves. Is there an "intended" flow for this review that I have no seen in documentation somewhere? A presentation or something?

thanks

SFII

Hello,

I have 4 requirements: ID#s 300-303. Status field is blank.

I placed them all in a review and they were reviewed and approved.

However, when a tester came in to look for Approved Requirements, these all still have Status of blank. Do they get modified at all during/after the review?

The review tool doesn't directly affect any Status attributes. This is by design, because (a) RRC doesn't necessarily know anything about the "Status" attribute within a project (there's no system "status" attribute), and (b) approval processes will vary, so we don't want to just assume that because something was approved in one review, it should be considered approved.

Being able to define an approval process is something we'd like to see in the future, but for now, it's up to the user to interpret the results of a review, and then manually change the Status to the appropriate value if necessary.