It's all about the answers!

Ask a question

RRDI reporting on custom attributes


Bharath M (5465428) | asked Jan 11 '12, 5:30 a.m.
Hi,

I was trying to create a report using RRDI which should display couple of custom fields. I came across this doc:
https://jazz.net/help-dev/clm/index.jsp?topic=%2Fcom.ibm.jazz.reports.doc%2Ftopics%2Fqm_t_customatt.html

If I follow the same procedure I'm getting duplicate rows in the result. In the sense, if there are 3 custom attributes defined, say ABC, XYZ and STU. I want to display the values of STU field. When I try to do that using the logic mentioned in the above doc, I get three rows of which only one row is what I need. If I'm not wrong the other two rows are coming because of the remaining two custom attributes. How can I suppress them?

Thanks,
Bharath

Accepted answer


permanent link
Peter Haumer (2.2k12019) | answered Jan 17 '12, 10:23 a.m.
JAZZ DEVELOPER
Hello.
(1) To avoid the empty rows using more than one custom attribute you
need to do a bit more work by creating a query for each custom attribute
with a detail filter (e.g. ='Cust Attr Name') instead of an
expression for a value. Then you need to join these queries together to
end up with one query, i.e. join the first custom attribute query with a
query on your artifact (e.g. test cases) and then do another join
joining the result of the first join with the second custom attributes.
You end up with one query that has columns for each custom attribute
(just as if you would write an SQL query to solve this) that you can
then drag/drop into a list table. I attached a sample report using
Insight 1.1 (Cognos 10) and a screen shot from the queries (Sources and
Stakeholder are the custom attributes defined for Test Cases in my
example).

(2) Create a query with a similar detail filter as in (1) and use that
for the value prompt.

Hope this helps,
Peter.



On 1/13/2012 7:38 AM, littleheartb4u wrote:
Thanks Peter. That worked. This leads to couple of more questions :).

1. How can we add more than one custom attribute of same type (Eg:
String Extension)to the table?

2. How to use a Custom Attribute as a input parameter?

Thanks,
Bharath
Ralph Schoon selected this answer as the correct answer

5 other answers



permanent link
Peter Haumer (2.2k12019) | answered Jan 11 '12, 12:53 p.m.
JAZZ DEVELOPER
Hello.
Often the simplest way of avoiding duplicate rows with empty fields is
to add groupings. I.e. if you have a table with Test Case Name, STU
columns then group by test case name.

Another way would be adding detail filters to remove rows in which the
custom attributes values are empty.

Hope this helps.
Peter.



On 1/11/2012 2:38 AM, littleheartb4u wrote:
Hi,

I was trying to create a report using RRDI which should display
couple of custom fields. I came across this doc:
https://jazz.net/help-dev/clm/index.jsp?topic=%2Fcom.ibm.jazz.reports.doc%2Ftopics%2Fqm_t_customatt.html

If I follow the same procedure I'm getting duplicate rows in the
result. In the sense, if there are 3 custom attributes defined, say
ABC, XYZ and STU. I want to display the values of STU field. When I
try to do that using the logic mentioned in the above doc, I get
three rows of which only one row is what I need. If I'm not wrong the
other two rows are coming because of the remaining two custom
attributes. How can I suppress them?

Thanks,
Bharath

permanent link
Bharath M (5465428) | answered Jan 13 '12, 10:29 a.m.
Thanks Peter. That worked. This leads to couple of more questions :).

1. How can we add more than one custom attribute of same type (Eg: String Extension)to the table?

2. How to use a Custom Attribute as a input parameter?

Thanks,
Bharath

permanent link
Bharath M (5465428) | answered Jan 17 '12, 3:38 a.m.
Hi,

Anything on this?

Thanks,
Bharath

permanent link
Bharath M (5465428) | answered Jan 18 '12, 1:29 p.m.
Thanks a lot for the tips Peter. But I can't find the attachments. Am I missing something?

Also, by using Joins, will it not affect the performance of the report?

-- Bharath

Hello.
(1) To avoid the empty rows using more than one custom attribute you
need to do a bit more work by creating a query for each custom attribute
with a detail filter (e.g. ='Cust Attr Name') instead of an
expression for a value. Then you need to join these queries together to
end up with one query, i.e. join the first custom attribute query with a
query on your artifact (e.g. test cases) and then do another join
joining the result of the first join with the second custom attributes.
You end up with one query that has columns for each custom attribute
(just as if you would write an SQL query to solve this) that you can
then drag/drop into a list table. I attached a sample report using
Insight 1.1 (Cognos 10) and a screen shot from the queries (Sources and
Stakeholder are the custom attributes defined for Test Cases in my
example).

(2) Create a query with a similar detail filter as in (1) and use that
for the value prompt.

Hope this helps,
Peter.



On 1/13/2012 7:38 AM, littleheartb4u wrote:
Thanks Peter. That worked. This leads to couple of more questions :).

1. How can we add more than one custom attribute of same type (Eg:
String Extension)to the table?

2. How to use a Custom Attribute as a input parameter?

Thanks,
Bharath

permanent link
Peter Haumer (2.2k12019) | answered Jan 18 '12, 9:53 p.m.
JAZZ DEVELOPER
Hello.
It seems that the jazz.net forum on the Website does not support
attachments. If you connect to the forum using an nntp client
(news.jazz.net) like Thunderbird then I hope you will see them. I do see
my own attachments when I loaded the latest messages just now. Using
Thunderbird for the forum will be so much more user-friendly as well.

About join performance: I don't think you will feel an impact as the
joins are done on the primary keys of the tables.

Peter.


On 1/18/2012 10:38 AM, littleheartb4u wrote:
Thanks a lot for the tips Peter. But I can't find the attachments. Am
I missing something?

Also, by using Joins, will it not affect the performance of the
report?

-- Bharath

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.