Regarding RQM reporting issue
Hi,
I am facing issues while generating the reports in Reports->View Reports->Requirements->Requirement Traceability. This report shows not only requirements but all the artifacts which are created in RRC like user story, functional Spec, use case diagram etc. Please guide.
I am not getting Requirement Type parameter to select.
Am using 3.0.1 version of RRC and RQM sitting in one JTS server
I am facing issues while generating the reports in Reports->View Reports->Requirements->Requirement Traceability. This report shows not only requirements but all the artifacts which are created in RRC like user story, functional Spec, use case diagram etc. Please guide.
I am not getting Requirement Type parameter to select.
Am using 3.0.1 version of RRC and RQM sitting in one JTS server
4 answers
I am running into the same issue.
Is there a resolution to this problem?
Is there a resolution to this problem?
Hi,
I am facing issues while generating the reports in Reports->View Reports->Requirements->Requirement Traceability. This report shows not only requirements but all the artifacts which are created in RRC like user story, functional Spec, use case diagram etc. Please guide.
I am not getting Requirement Type parameter to select.
Am using 3.0.1 version of RRC and RQM sitting in one JTS server
Hello.
We added the Requirement Type parameter for the upcoming 4.0 release,
which is now in Beta.
Peter.
On 3/5/2012 12:40 PM, sipocz wrote:
We added the Requirement Type parameter for the upcoming 4.0 release,
which is now in Beta.
Peter.
On 3/5/2012 12:40 PM, sipocz wrote:
I am running into the same issue.
Is there a resolution to this problem?
chandrahasawrote:
Hi,
I am facing issues while generating the reports in Reports->View
Reports->Requirements->Requirement Traceability. This report
shows not only requirements but all the artifacts which are created
in RRC like user story, functional Spec, use case diagram etc. Please
guide.
I am not getting Requirement Type parameter to select.
Am using 3.0.1 version of RRC and RQM sitting in one JTS server