Introduce a new JQL function that returns Test Executions where all associated Test Runs are in a final or specific status (e.g., Passed, Failed)

Description:
Currently, Xray for Jira Cloud does not offer a JQL function that allows users to query Test Executions whose Test Runs have all reached a final state. Since Test Run Status is not stored as a custom field in Jira, there are no triggers or webhooks available when Test Run statuses change. This limitation blocks users from building automations such as automatically transitioning or resolving Test Executions once all Test Runs are complete.
User friction:

• No available trigger or webhook for Test Run Status changes.
• Jira Automations cannot detect when all Test Runs under a Test Execution have reached a final status.
• Users cannot set up automated transitions or resolution workflows based on Test Run completion.
• Current JQL functions focus on Tests, not the aggregate status of Test Runs within a Test Execution.
  Steps to reproduce (right now) / Actual Result:
  We observe that no existing function supports this use case. Automation rules cannot be configured reliably because no field or no event reflects the final Test Run status.
   
  IMPACT

What would improve if solved:{}

• Users can build reliable Jira Automation to close, transition, or update Test Executions when all Test Runs are complete.
• Reduces effort in monitoring Test Execution completion.
• Improves reporting accuracy by enabling automation-driven workflow transitions.
• Enhances traceability and CI/CD integration, where automated pipelines need to react to completed Test Executions.
  Impact on stakeholders:
• QA teams: Better visibility and automated workflow transitions.
• Project managers: More accurate reporting of testing progress.
• DevOps teams: Ability to integrate with CI/CD tools based on Test Execution readiness.
• Automation users: Unlocks use cases currently blocked by missing triggers.
  Current workaround:
• Manually transition or update those Test Executions.
• Monitor Test Run statuses using a scheduled job.
• Use Dashboards or Test Run reports to identify Test Executions with all runs completed.
• Highly error‑prone and not scalable.
  CONTEXT & EXAMPLES:

Concrete example:
A team wants to automatically transition a Test Execution to "Done" when all associated Test Runs reach the "Passed" status.

Expected automation flow:

• Pipeline completes → Test Runs updated → Jira detects final status → Test Execution transitions automatically.

Current limitation:

• There are no triggers for TestRun Status changes, and hence no direct automation rule can be applied. Also, no JQL function or trigger can detect this state, so the automation rule cannot run.
  Workaround risk:
• Human error
• Delayed reporting
• Broken automation flows
• Inconsistent Test Execution states across projects