Display Test Run Status changes in Xray History sections across related issues (Test and Test Execution)

Description
Introduce the ability for Test Run Status changes to be reflected and visible in the Xray History sections of related issues, such as the Test and Test Execution issues.

Currently, when a status update is performed on a Test Run, the change is only visible in the context/page where the update was made (Test Run Activity section). The related Test or Test Execution Xray History section does not reflect these updates, even though the Test Run belongs to and impacts those entities.

Providing visibility of Test Run status transitions in related Xray History sections would improve traceability, auditing, and overall user visibility into execution activity across linked Xray entities.

The enhancement could include:

• Recording Test Run status transitions in related issue histories
• Showing who performed the change
• Including timestamps
• Indicating the source/context where/how the change occurred

This would provide a more complete and centralized activity timeline for users reviewing Tests and Test Executions.

User friction
Users currently lack centralized visibility into Test Run status changes when reviewing related Test or Test Execution issues.

Although changes are successfully applied, the history information is fragmented and only visible within the context of the modification (Test Run Activity). This creates confusion and reduces traceability during audit execution.

Users may incorrectly assume:

• No updates occurred
• Statuses were not modified
• Execution activity is missing

Steps to reproduce:
1. Open a Test Execution issue.
2. Update the status of a Test Run.
3. Navigate to the related Test issue or Test Execution Xray History section.
4. Review the displayed history entries.

Actual Result:
The Test Run status change is reflected only on the page/context where the update was performed and does not appear in the Xray History sections of related issues.

This is currently expected behavior.

IMPACT

• Reduced visibility into execution activity
• Limited auditability of Test Run changes
• Lower traceability across related Xray entities

What would improve if solved:

• Centralized visibility of Test Run status activity
• Improved audit trails
• Better traceability across Tests and Test Executions
• Easier execution analysis
• Increased transparency for teams reviewing historical execution changes
• Improved user experience when navigating related Xray entities

Impact on stakeholders:

• Better understanding of execution progression
• Easier review of Xray historical status transitions
• Improved audit and reporting capabilities
• Better visibility into testing activity
• Reduced confusion regarding missing history entries
• Improved traceability for compliance or operational reviews

Current workaround:
Users must manually:

• Open individual execution (Test Runs)
• Compare statuses across issues
• Review execution details separately
• Correlate timestamps and updates manually

CONTEXT & EXAMPLES:
This enhancement would be especially useful in environments where:

• Multiple teams review Test Executions
• Auditability and traceability are important
• Large execution cycles generate many Test Run updates
• Teams rely heavily on issue history for operational tracking

The feature would help create a more complete historical timeline within Xray issue histories.

Concrete example:
A QA lead reviews a Test Execution issue to understand recent testing activity.
Several Test Run statuses were updated by testers during execution, but the Xray History section in Test Execution does not reflect these changes.
The QA lead must manually open execution details and inspect individual Test Runs to understand what changed and when.
If Test Run status transitions were reflected in the related Xray History sections, the QA lead could immediately review the full execution activity timeline directly from the Test Execution issue.