Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

RRC Reviews - Expected Behavior?

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?

1

0 votes



3 answers

Permanent link
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.

1 vote


Permanent link
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.

0 votes


Permanent link
Sterling,

I don't think there's any documentation specifically on the workflow. If you are using a collection, and you decide that the artifacts in it are ready to change state based on the results of the review, you can do this from within the collection:
* open the collection
* select all artifacts in it
* open a context menu (pencil icon) on one of them
* choose Change Attributes for n Artifacts
* choose the attribute you want to change (e.g., Status) and set the value you want.

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: May 11 '12, 11:41 a.m.

Question was seen: 4,053 times

Last updated: May 11 '12, 11:41 a.m.

Confirmation Cancel Confirm