Description
Description
As a user of Xray reporting gadgets, I want custom Test Types to be displayed as dedicated columns in the Test Executions Report/Test Executions List gadget and Test Plans Report, so that reporting accurately reflects the Test Type configuration defined in the system.
User friction
Organizations that customize Test Types cannot distinguish their custom Test Types in reports because they are grouped under the generic "Other" column. This reduces report accuracy and limits visibility into execution progress by Test Type.
Steps to reproduce (right now) / Actual Result:
- Configure one or more custom Test Types in Xray.
- Create Tests using the custom Test Types.
- Open the Test Executions Report/Test Executions List gadget or Test Plans Report
- Review the Test Type columns.
IMPACT
Reporting does not fully honor the configured Test Type taxonomy, making it difficult to track progress and execution metrics for custom Test Types.
What would improve if solved:
- Reports would accurately reflect the organization's configured Test Types.
- Improved visibility and traceability of testing activities.
- More meaningful dashboards and stakeholder reporting.
- Reduced need for manual analysis and report customization.
Impact on stakeholders:
Test Managers, QA Leads, Project Managers, and stakeholders relying on dashboard metrics cannot accurately analyze results by custom Test Type.
Current workaround:
There is no direct workaround. Users must manually interpret data grouped under the "Other" category or create external reports to differentiate custom Test Types.
CONTEXT & EXAMPLES:
Xray allows administrators to create and use custom Test Types. However, reporting gadgets continue to recognize only the predefined Test Types (Manual, Cucumber, and Generic) as separate columns while aggregating all custom Test Types into "Other".
Concrete example:
An organization defines the custom Test Types:
- API Test
- Performance Test
- Security Test
In current reports, all three Test Types are counted under "Other" instead of appearing as individual columns, preventing stakeholders from viewing execution progress for each Test Type separately.
Workaround risk:
Grouping custom Test Types into "Other" can lead to inaccurate reporting, reduced visibility, and manual reporting efforts, increasing the risk of misinterpreting testing progress and coverage.
Â