Static Artifacts Version in Collection
When looking at the help for my RRC 4.0.2 I see this:
-
Capture the approved version of a set of requirements. For example, you can capture a set of artifacts that have been approved in a formal review. You can then work on changes to the requirements while the collection continues to show only the approved versions.
(Managing and composing requirements >> Working in the web client >> Defining requirements >> Collections)
Attempting to actually do this, it didn't work.
- I created a Formal Review for an Artifact.
- Approved the Review.
- Created a Collection from it.
- Changed the Requirement.
- Looked in the Collection and it held the CHANGED version (not the approved version).
Has anyone been able to make this work? If so, how?
I recall seeing other topics about the same issue on this forum which confirm my experience (and further contradict what's in the help page) but couldn't find them.
2 answers
There may be other ways, but in RRC V4.0.4, I know of only 2 ways to see specific artifacts versions, one is to view it via the review editor where the artifact version is recorded as part of the formal review and the other is to create a project baseline with a time stamp of when the review was approved and the collection created, and open that collection via the project baseline history editor.
Now a baseline can be created at any time, with any time stamp in the past, just set the time to be same as when the collection for the approved review was created.
Now a baseline can be created at any time, with any time stamp in the past, just set the time to be same as when the collection for the approved review was created.
Comments
Hey Taly..thanks for pointing out that flaw in the V402 documentation. We have since identified that error and fixed it in in the V403 and subsequent docs.
My understanding of V402 (and I could be dead wrong about this) was that collections enabled you to capture
artifacts at their latest or "live" revision level or at the revision level that was captured in a project snapshot.
(I thought the snapshot feature was built into the collections window). But again, I am just going from my (flawed) memory about V402.
What I do know for sure was that that feature was removed from the product for various reason and that collection artifacts are now always live artifacts.
At any rate, thanks again for pointing out the doc issue and I hope the workarounds that Robin Bater provided were helpful!
Bruce Korn
My understanding of V402 (and I could be dead wrong about this) was that collections enabled you to capture
artifacts at their latest or "live" revision level or at the revision level that was captured in a project snapshot.
(I thought the snapshot feature was built into the collections window). But again, I am just going from my (flawed) memory about V402.
What I do know for sure was that that feature was removed from the product for various reason and that collection artifacts are now always live artifacts.
At any rate, thanks again for pointing out the doc issue and I hope the workarounds that Robin Bater provided were helpful!
Bruce Korn