Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-15353

Board Filters can end up with invalid JQL when underlying data used in the query are deleted or modified

    • Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • None
    • 1
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Summary

      Board Filters can end up with invalid JQL syntax when the underlying data of the query is modified or removed. e.g. a component that is referenced gets removed or renamed, an issue key that is referenced is deleted, etc etc.

       

      Steps to Reproduce

      1. Access your project board
      2. Choose Board > Configure > Filters
      3. Edit or Create a Filter with a valid query and Save.
      4. The Board will display data as expected
      5. Invalidate the query created in Step 3 by modifying some meta data in JIRA that is referenced in the query
      6. This will error out in the issue navigator where the query is validated before execution
      7. since the query was valid when it was saved; it stays set in the Board Config. 
      8. When you access the Board - no Data is Displayed

      Expected Results

      There should be an error on the Board saying the underlying query in INVALID.

      Actual Results

      The Board displays no data without any errors or warnings. 

       

            [JSWSERVER-15353] Board Filters can end up with invalid JQL when underlying data used in the query are deleted or modified

            Atlassian Update – 03 October 2019

            Hi,

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers).

            We hope you will appreciate our candid and transparent communication and our attempts to become more transparent about our priorities. Making tradeoffs and saying no is never an easy task to perform. You can read more about our approach to highly voted server suggestions here.

            To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing Recently resolved issues and Current work and future plans.

            Regards,
            Jira Server and Data Center Product Management

            Gosia Kowalska added a comment - Atlassian Update – 03 October 2019 Hi, Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers). We hope you will appreciate our candid and transparent communication and our attempts to become more transparent about our priorities. Making tradeoffs and saying no is never an easy task to perform. You can read more about our approach to highly voted server suggestions here . To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing Recently resolved issues and Current work and future plans . Regards, Jira Server and Data Center Product Management

            Vik added a comment - - edited

            npellow

            "project = DATA OR component = Data AND type in (Epic, Bug, Task, Improvement, "New Feature") ORDER BY Rank ASC"

             The customer removed the "component = DATA" so the query does not return anything and errors out when run in issue navigator or when defining a filter;

            but since this filter is already present on the Board; when trying to view the Board - nothing loads. 

             

            By invalidating the query - I mean deleting one or more entities that the query relies on. 

            Vik added a comment - - edited npellow "project = DATA OR component = Data AND type in (Epic, Bug, Task, Improvement, "New Feature") ORDER BY Rank ASC"  The customer removed the "component = DATA" so the query does not return anything and errors out when run in issue navigator or when defining a filter; but since this filter is already present on the Board; when trying to view the Board - nothing loads.    By invalidating the query - I mean deleting one or more entities that the query relies on. 

              Unassigned Unassigned
              vgambhir Vik
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: