Overall Execution Status should support “Attachments (N)” column for Test Step attachments

Description

Problem Statement:
Currently, in Xray Cloud, the “Overall Execution Status” section within a Test Execution does not allow adding a column that displays the number of attachments added at the Test Step level of a Test issue. Users cannot visualize how many attachments are associated with each Test Run directly from this view.

This affects teams who rely on step-level evidence attachments (e.g., screenshots, logs) and need visibility into whether execution evidence has been provided.

User Friction

• Users cannot see the count of Test Step attachments per Test Run in the Overall Execution Status section.
• There is no column option to display “Attachments (N)” from Test Steps.
• Users must manually open each Test Run and inspect individual Test Steps to verify whether attachments were added.
• This is inefficient, especially in large Test Executions with many tests and steps.

Steps to Reproduce

1. Open a Test Execution in Xray Cloud.
2. Navigate to the Overall Execution Status section.
3. Attempt to customize columns using the column filter option.
4. Observe that there is no option to add a column displaying the number of attachments from Test Steps.
5. To check attachments, users must open each Test Run and manually inspect Test Steps.

Expected Behavior

Users should be able to:

• Add an “Attachments (N)” column in the Overall Execution Status section.
• View the number of attachments associated with Test Steps only (not from Test issue or Test Execution level).
• Quickly assess whether execution evidence was provided, without needing to open each Test Run.

IMPACT

What would improve if solved:

• Faster validation of execution evidence.
• Improved visibility into Test Run completeness.
• Reduced manual navigation effort in large Test Executions.

Impact on stakeholders:

• QA Engineers validating step-level evidence.
• Test Managers reviewing execution quality.
• Teams working in regulated environments where attachment evidence is mandatory.

Frequency:

Occurs whenever teams need to verify whether Test Step attachments were provided during execution.

Current Workaround

• Manually open each Test Run.
• Inspect individual Test Steps to check for attachments.