Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-79878

Provide a user friendly error message if a JQL query for a board times out on the database

      Issue Summary

      Setting a filter on the board that is not properly formatted (The query is too complex and can be simplified) causes the JQL to timeout on the database. After the timeout, the board doesn't load without any error messages.

      Steps to Reproduce

      1. Create a complex JQL query that will timeout on the database.
      2. Associate the JQL query with the board filter.

      Expected Results

      1. The board properly loads.
      2. If the board fails to load, it presents an error message with an explanation of why it failed to load.

      Actual Results

      The board will not load and does not provide an error message why it did not load.

      Workaround

      Optimizing the JQL query so it does not timeout on the database.

            [JRACLOUD-79878] Provide a user friendly error message if a JQL query for a board times out on the database

            Atlassian Update - October 25, 2023

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!
            Jira Cloud team

            Matthew Hunter added a comment - Atlassian Update - October 25, 2023 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team! Jira Cloud team

            I was informed by support that "advanced issue search" and board settings screens are using different way to collect results from database (even the same JQL runs ok on filter search and fails on board settings screen). 

            On board settings screen when jql fails - no message is shown to end user and spinner continiues to spin. This should be fixed and error message should be raised in that case (similar like in filter search case).

            Paweł Wadas added a comment - I was informed by support that "advanced issue search" and board settings screens are using different way to collect results from database (even the same JQL runs ok on filter search and fails on board settings screen).  On board settings screen when jql fails - no message is shown to end user and spinner continiues to spin. This should be fixed and error message should be raised in that case (similar like in filter search case).

              Unassigned Unassigned
              2711b2aa3c24 Barışcan Elkama
              Affected customers:
              1 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: