Support grouping by Jira Assets (Object) custom fields in Overall Test Coverage / Tests by Coverage gadget

Problem Statement: Overall Test Coverage / Tests by Coverage dashboard gadget currently allows grouping only by Jira system fields and standard Select List custom fields. Jira Assets (formerly Insight) object custom fields do not appear in the Group by dropdown.

This limitation prevents teams from analyzing test coverage using business-critical dimensions that are commonly modeled as Assets, such as applications, services, systems, or environments. As a result, users cannot build meaningful coverage KPIs aligned with how their organization structures its IT landscape.In Xray Cloud, the 

User Friction:

• Jira Assets are widely used to model real-world entities (e.g., Application, Service, Component).
• Xray can store Assets values on Tests and Test Executions, but:
  • These fields cannot be selected in the Group by dropdown.
  • There is no indication in the UI or documentation that Assets fields are unsupported.

• Users expect Assets fields to behave similarly to other single-value categorical fields used for reporting.
• This forces teams to duplicate data into Select List fields purely for reporting purposes, increasing maintenance overhead and the risk of inconsistent data.

Steps to Reproduce (Workflow)

1. Create or use an existing Assets object custom field (single value), e.g. EOE IT App Name.
2. Add the Assets field to Xray issue screens (Test / Test Execution).
3. Populate the field with Assets objects.
4. Configure the Overall Test Coverage / Tests by Coverage gadget.
5. Open the Group by dropdown.

• Observe that:
  • Jira system fields and Select List custom fields are available.
  • The Assets object custom field is not listed.

Expected Behavior

• Assets (object) custom fields should be available in the Group by dropdown or

• Clear documentation should explicitly state that Assets fields are not supported for grouping in Xray gadgets.

Actual Behavior

• Assets object custom fields do not appear in the Group by dropdown.

• There is no UI indication or documentation explaining this limitation.

Impact

What would improve if solved

• Teams could group test coverage by real business entities (applications, services, systems).

• Dashboards would better reflect how organizations structure ownership and responsibility.

• Reduces the need for duplicate Select List fields used solely for reporting.

• Improves the value of Xray dashboards for management and audit reporting.

Impact on Stakeholders

• QA Managers and Test Managers building coverage dashboards.

• Project and Engineering Leads tracking test coverage per application or system.

• Organizations heavily invested in Jira Assets / JSM CMDB modeling.

This issue occurs repeatedly whenever teams attempt to align Xray reporting with their Assets-based data model.

Current Workarounds

• Duplicate Assets data into a Select List custom field purely for grouping

• Perform coverage analysis in external reporting tools

• Avoid using Assets for reporting dimensions, limiting their usefulness within Xray dashboards.

All workarounds introduce extra maintenance, data duplication, or loss of reporting fidelity.

Context & Example

Concrete example:
A QA team assigns an Assets field (Application Name) to all Tests. Management wants to see test coverage grouped by application in the Overall Test Coverage gadget. While the field is populated and visible on issues, it cannot be selected in Group by, making the dashboard unusable for this purpose. The team is forced to recreate the same data as a Select List field solely for reporting.

Workaround risk:
Maintaining parallel fields (Assets + Select List) increases the chance of mismatched or outdated values, especially in large or regulated environments.