There are two query subjects of interest: Request Related Requests, which is based on the parent/child links, and Request Related Requests (by Relational Link) (RRRbRL) which is based on all other types of link.

When you're querying based on the relational link query subject, the thing to take into consideration is that work items will either fall into the "left" or "right" side of the relationship based on where the link was created from. For example, if you want to query for all stories and related defects, the story might either be in the Request, or the Request Related Request (by Relational Link) query subject after the join is performed.

To solve this you need to create two query subjects in Insight/RRDI, the first needs to filter on Request.Type = 'Story' and RRRbRL.Type = 'Defect' and another that filters on Request.Type = 'Defect' and RRRbRL.Type = 'Story'. You can then union these queries to get a single query subject that has all of the stories/defects that are related.

The issue you'll have with the union query is that in the "left" columns you'll have some stories, and some defects, and the same on the right. You will need to edit the expressions of the data items to ensure that you end up with one type of work item on the left, and the other type on the right.

Hi,

we are trying to build some RRDI-RTC reports that should report on the relational links of a workitem. For eg: Give me list of workitems of type A which has a related workitem of type B. The relation can be Child or just Related.

Though the report returns results, I see some difference in the list when I compare the report results and normal query results. The report returns less number compared to the queries.

I'm using Request and Request related Requests (by Relational Link) to get the report data.

Am I missing something here?

Regards,
Bharath

Just the plain Request.Type field.

There are two query subjects of interest: Request Related Requests, which is based on the parent/child links, and Request Related Requests (by Relational Link) (RRRbRL) which is based on all other types of link.

When you're querying based on the relational link query subject, the thing to take into consideration is that work items will either fall into the "left" or "right" side of the relationship based on where the link was created from. For example, if you want to query for all stories and related defects, the story might either be in the Request, or the Request Related Request (by Relational Link) query subject after the join is performed.

To solve this you need to create two query subjects in Insight/RRDI, the first needs to filter on Request.Type = 'Story' and RRRbRL.Type = 'Defect' and another that filters on Request.Type = 'Defect' and RRRbl.Type = 'Story'. You can then union these queries to get a single query subject that has all of the stories/defects that are related.

The issue you'll have with the union query is that in the "left" columns you'll have some stories, and some defects, and the same on the right. You will need to edit the expressions of the data items to ensure that you end up with one type of work item on the left, and the other type on the right.

Hi,

we are trying to build some RRDI-RTC reports that should report on the relational links of a workitem. For eg: Give me list of workitems of type A which has a related workitem of type B. The relation can be Child or just Related.

Though the report returns results, I see some difference in the list when I compare the report results and normal query results. The report returns less number compared to the queries.

I'm using Request and Request related Requests (by Relational Link) to get the report data.

Am I missing something here?

Regards,
Bharath

Thanks Jared. Thats very useful info. When you say Request.Type = 'Story', are you saying Request Related Requests.Type or just Request.Type