Hello, our company wants to try to see how it would work if we start writing web specs in QC under requirement. One of the challenges of doing so is not being able to print out the specs easily. I still can not figure out a way to print just a section of the requirements. For example, select a requirement and generate a report to include it and all of its child requirements. Can you do that? If so, how? Thanks!
Filtering would probably be your best option here. Suggestion would be to set a user field containing a requirements hierarchy. Perhaps something like [system][subsystem][release][change request nr][requirement nr] (eg. Accounting_GL_2.9_1298_R1.1.3).
Carry the hierarchy along on child requirements with extension:
Then, filtering on Accounting_GL_2.9* will report all requirements and child requirements associated with that release.
There is a little work involved in setting such a filtering option up, but it provides a good deal of flexibility and overcomes some of the limitations present in the Requirements tab of TD.
I don't know if I'm understanding this correctly. Do you mean we should follow a standard in the naming for the requirement and then filter on the name? Right now the requirements are already put in and it does not really follow this naming convention.
You can filter on any available field.
My suggestion would be to define an additional field for managing the requirement hierarchy for filtering purposes. Unless you are including a requirement number or similar traceable piece of data, the requirement name itself won't be too useful. Where that might work is if, for example, your requirement name convention was to use a document reference prefix to establish the necessary hierarchy. You will need to make an assessment of impact from changing the naming convention vs adding a new field.
right now we figured out a work around. basically if i convert the selected requirements to test plan and then use the advance filter of the requirements to filter based on test plan, it will work ok. we are thinking about adding a new custom field in the future.