Uploaded image for project: 'Xray for Jira'
  1. Xray for Jira
  2. XRAY-11751

Requirement Traceability Report throwing "JQL Failure Detected" Error

    XporterXMLWordPrintable

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • Xray DC 8.5.1
    • None
    • Report
    • None
    • Jira Data Center: 11.3.11

      Xray: 8.5.1 initially reported; issue persists on 8.5.2

    • UNCOVERED

    Description

      Description: 

      On Jira DC, encountering a "JQL Failure Detected" error when accessing the Requirement Traceability Report.

      The issue was first reported after upgrading to Xray 8.5.1 and continues to occur after upgrading to Xray 8.5.2.

      The Jira JQL resilience settings was configured based on Atlassian's recommendation:

      • Search results limit: 10,000
      • Memory circuit breaker: 95%

      Pre-conditions: 

      • Jira Data Center 11.3.11
      • Xray 8.5.1 / 8.5.2
      • Large Jira instance/dataset
      • JQL resilience settings configured:
        • jira.search.platform.max.result.window=10000
        • jira.lucene.search.memory.circuit.breaker.percentage=95

       

      How to reproduce

      1. Configure Jira Data Center with the following settings:
        • jira.search.platform.max.result.window=10000
        • jira.lucene.search.memory.circuit.breaker.percentage=95
      1. Restart Jira.
      1. Open the Requirement Traceability Report in Xray.
      1. Run the report.
      1. Observe the error.

      Actual result/Attachments:

      The Requirement Traceability Report fails with:

      "JQL Failure Detected"

      The issue occurs in the customer's environment but could not be reproduced locally with the same configuration.

      Customer logs/screenshots/HAR can be attached for further investigation

      Expected result:

      The Requirement Traceability Report should execute successfully without displaying the "JQL Failure Detected" error.

      Version

      • Jira Data Center: 11.3.11
      • Xray: 8.5.1 initially reported, 8.5.2 currently
      • JQL resilience settings:
        • jira.search.platform.max.result.window=10000
        • jira.lucene.search.memory.circuit.breaker.percentage=95

      Workaround

       

      Attachments

        Issue Links

          Activity

            People

              joana.fonseca Joana Fonseca
              mudedlla.chandraveena Mudedlla Chandraveena
              Votes:
              3 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: