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

Cannot use JQL In Escalation Service because of failed: Add JQL LIMIT support

XMLWordPrintable

    • 7
    • 16

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      The JQL query language lacks the possibility to return a limited number of issues from a search, compare with SQL LIMIT or TOP statements.

      This would be very valuable when you want to get e.g. the 10 highest ranked stories.

          Form Name

            [JRACLOUD-68133] Cannot use JQL In Escalation Service because of failed: Add JQL LIMIT support

            David Moreno added a comment -

            Yes please implement this

            David Moreno added a comment - Yes please implement this

            Yatish Madhav added a comment -

            Yes, please again ...

            Yatish Madhav added a comment - Yes, please again ...

            Douglas Tseng added a comment -

            this is a must needed function to really make automation rule useful.

            not understanding why the past tickets or other similar tickets were closed w/ a resolution of "won't fix".

            the natively restricted daily processing service limits is way too low for today's workload when trying to automate stuff and not being able to batch process requests as a work around by querying and limiting amount of issues is so backwards when there is a hard limit of such a low daily processing service limit time.

             

            Douglas Tseng added a comment - this is a must needed function to really make automation rule useful. not understanding why the past tickets or other similar tickets were closed w/ a resolution of "won't fix". the natively restricted daily processing service limits is way too low for today's workload when trying to automate stuff and not being able to batch process requests as a work around by querying and limiting amount of issues is so backwards when there is a hard limit of such a low daily processing service limit time.  

            Yatish Madhav added a comment -

            I added a vote and watched the linked issue ... +1 I am finding more and more use cases to have the LIMIT option on JQL statements. Please advise or suggest a workaround please? Thank you

            Yatish Madhav added a comment - I added a vote and watched the linked issue ... +1 I am finding more and more use cases to have the LIMIT option on JQL statements. Please advise or suggest a workaround please? Thank you

            Raul van der Raaf added a comment -

            Really need this functionality. Jira Automation now cannot properly work with 1 result but works with a list when it is not needed.

            Being able to LIMIT or TOP the results to 1, might remove unneeded stress from Jira Automation (or the Atlassian Cloud Servers) as well.

            This would be a WIN - WIN, for Atlassian and for us.

             

             

            Raul van der Raaf added a comment - Really need this functionality. Jira Automation now cannot properly work with 1 result but works with a list when it is not needed. Being able to LIMIT or TOP the results to 1, might remove unneeded stress from Jira Automation (or the Atlassian Cloud Servers) as well. This would be a WIN - WIN, for Atlassian and for us.    

            Mark Segall added a comment -

            This capability would also serve the evolution of automation.  Sometimes Jira Admins need to do a one-time bulk change to projects with tens (hundreds) of thousands of issues (e.g. data previously captured in a custom select field being moved to an Insight field). It would be advantageous to be able to leverage automation and execute in batches rather than getting throttling errors or worse... having to revert back to the painful process of exporting everything to csv and importing in batches of 1,000.

            Mark Segall added a comment - This capability would also serve the evolution of automation.  Sometimes Jira Admins need to do a one-time bulk change to projects with tens (hundreds) of thousands of issues (e.g. data previously captured in a custom select field being moved to an Insight field). It would be advantageous to be able to leverage automation and execute in batches rather than getting throttling errors or worse... having to revert back to the painful process of exporting everything to csv and importing in batches of 1,000.

            Al Berjanskii added a comment -

            Please consider reopening JRACLOUD-31384 and implementing a LIMIT feature, it would be useful when writing Jira Automations to limit the number of results processed from a JQL.

            Al Berjanskii added a comment - Please consider reopening  JRACLOUD-31384 and implementing a LIMIT feature, it would be useful when writing Jira Automations to limit the number of results processed from a JQL.

            Arleena Faith added a comment -

            The Escalation Service uses JQL results and executes each time per match. JQL does not have a "LIMIT" which causes Escalation services scripts to unwantedly execute more than one.

            Fix this by adding a much needed JQL limit feature.

            Arleena Faith added a comment - The Escalation Service uses JQL results and executes each time per match. JQL does not have a "LIMIT" which causes Escalation services scripts to unwantedly execute more than one. Fix this by adding a much needed JQL limit feature.

              Unassigned Unassigned
              c9ef012b9a05 Arleena Faith
              Votes:
              75 Vote for this issue
              Watchers:
              35 Start watching this issue

                Created:
                Updated: