Using the Group by Component´s option on Overall Requirement Coverage Gadget does not display grouped components with the same name if they are from different projects

Description
Using the Group by Component´s option on Overall Requirement Coverage Gadget does not display grouped components with the same name if they are from different projects.
If the filter used in the gadget pulls Requirement Issues from different projects that have both a component with the same name and we choose to Group by Component, the gadget will not group/combine this components results into 1 group, rather it will pick only the results from one of the projects components.

 

Pre-conditions

Having at least 2 different Requirement Projects

 

How to reproduce

1. Create a component for each project. The component must be named the same in both projects.

1. Create a requirement issue for each project, adding the component to it.
2. Add a Test to each Requirement, so it have Test Coverage.

1. Create an Issue filter searching for all the Requirements in both projects with the same component name.

1. Create an Overall Requirement Coverage Gadget using this filter and Group the gadget by Components.

Actual result/Attachments

The gadget does not combine the results from both projects into the same component group, nor separate the components as 2 different groups, rather it picks results from just one project.

Expected result

The gadget should group/combine all the results from both projects into the same component name, as it is done with the Group by Status. Or it should separate the results into 2 different groups with the same name, one for each project component.

 

 

Version

• Xray v7.5.1-j9