Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-16182

Queries using the Development custom field are not considered valid queries.

XMLWordPrintable

      Summary

      Queries using the Development custom field are not considered valid queries by JIRA JQL assistant.

      Environment

      Cloud

      Steps to Reproduce

      1. Create a query like this in the Issue search: 
        development[pullrequests].all > 2

      Expected Results

      This is a valid query and JIRA should show the user a green arrow indicating the query is valid.
      The result of the query should be displayed to the user.

      Actual Results

      The results appear to be retrieved correctly, but JIRA is considering this syntax as an invalid syntax:

      NOTES:

      Seems to be affecting Bulk Edits based in this query as well.

      Workaround

      None.

        1. invalidQuery.png
          invalidQuery.png
          9 kB

            [JSWCLOUD-16182] Queries using the Development custom field are not considered valid queries.

            Dylan added a comment -

            Due to an extended period of inactivity and low interest this bug has been auto-closed. If you’re still experiencing this issue, please comment and we’ll re-open to triage.

            Cheers,

            Atlassian

            Dylan added a comment - Due to an extended period of inactivity and low interest this bug has been auto-closed. If you’re still experiencing this issue, please comment and we’ll re-open to triage. Cheers, Atlassian

            Jason Bender added a comment -

            Was this fixed in the most recent cloud release?

            Jason Bender added a comment - Was this fixed in the most recent cloud release?

            Jason Bender added a comment -

            I can tell you that I do not consider this a Low priority. We use these parameters to identify tickets that have pull requests, etc. which is part of our workflow.

            When can we expect this to be resolved?

            Jason Bender added a comment - I can tell you that I do not consider this a Low priority. We use these parameters to identify tickets that have pull requests, etc. which is part of our workflow. When can we expect this to be resolved?

              Unassigned Unassigned
              aborzzatto Andre Borzzatto
              Affected customers:
              2 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: