It's all about the answers!

Ask a question

artifact counts in RRDI

ross jones (492631) | asked Nov 12 '13, 12:39 p.m.

Has anyone experienced the following?

I have run across a behavior of RRDI [which i consider a defect] related to counting artifacts of type requirement [it may apply to other types as well].

The behavior is that when RRDI is asked to count the artifacts of type requirement, it counts the number of unique instances of the data warehouse field "requirement ID", rather than the data warehouse field "reference ID". Reference ID is the unique identifier for artifact, while "requirement ID" is unique identifier of EACH INSTANCE of the artifact, i.e. if you use the artifact in multiple locations in RM, e.g. module, collection, etc., RRDI returns the count of each time it is used rather than the true unique number of requirements. This behavior causes my reports to return the wrong number [count] for some reports I am running.

ross jones commented Feb 24 '14, 1:05 p.m.

this is now being worked as Defect 80062

One answer

permanent link
Erica Tran (1.4k7) | answered Feb 25 '14, 11:57 a.m.
Hi Ross,

Could you provide the full URL of the defect?  I'm not sure which repository the record is in.  This would help for others looking for this issue. 

I just want to note that the page Reporting Quick Tips has a video on Counting the requirements using the identifier field.  Maybe this would help. 


Francesco Chiossi commented Feb 25 '14, 12:14 p.m.

Defect 80062 Requirement count metrics show inaccurate results

Erica Tran commented Feb 25 '14, 12:30 p.m.

Thanks Francesco.

ross jones commented Feb 25 '14, 3:57 p.m.

ross jones commented Feb 25 '14, 4:35 p.m.

I have [finally] viewed Petru's video of creating a report to count reference IDs. thank you. It looks like the report described in the video will provide the data I am needing.............however, I need that data vs time, days weeks, months. and the "out of the box RRDI report is still wrong [per my definition of reqs counting], and while Petru's custom report will work, it takes a sophisticated report engineer to build it. I will also note that, IMHO, the term "requirements type" in the video is Very misleading...........I believe a better term is "artifact type".              In any case I look forward to resolution of this issue.

Your answer

Register or 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.