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

Add JQL LIMIT support

XMLWordPrintable

    • 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.

            [JRACLOUD-31384] Add JQL LIMIT support

            Yatish Madhav added a comment -

            +1 yes, please ... I have a use case where I want to add a JQL to a scheduled automation rule BUT want to only run it on 10 issues at a time. Please advise? Thank you

            Yatish Madhav added a comment - +1 yes, please ... I have a use case where I want to add a JQL to a scheduled automation rule BUT want to only run it on 10 issues at a time. Please advise? Thank you

            Eduardo Alfaro added a comment -

            I think it's useful too. Please, consider reopen this request.

            Eduardo Alfaro added a comment - I think it's useful too. Please, consider reopen this request.

            Sivan Tal added a comment -

            I have a need to find the highest value of some custom field across a project's issues.

            The way I do it is to query all the project's issues, ordered by that field value, and I see it in the first result. But getting all the issues just to see the first one is inefficient.

            Sivan Tal added a comment - I have a need to find the highest value of some custom field across a project's issues. The way I do it is to query all the project's issues, ordered by that field value, and I see it in the first result. But getting all the issues just to see the first one is inefficient.

            Al Berjanskii added a comment -

            A LIMIT function would be useful to implement so that we can have Jira Automation act on a set of items from a JQL query. Please consider reopening this request.

            Al Berjanskii added a comment - A LIMIT function would be useful to implement so that we can have Jira Automation act on a set of items from a JQL query. Please consider reopening this request.

            シムカ added a comment -

            hey, lazy asses .. implement this already!

            シムカ added a comment - hey, lazy asses .. implement this already!

            Jonas Larsen added a comment -

            Please reopen this!

            It's implemented in the REST API (with startAt and maxResults), so why not add the functionality to JQL as well?

            Jonas Larsen added a comment - Please reopen this! It's implemented in the REST API (with startAt and maxResults), so why not add the functionality to JQL as well?

            Bill Tanner added a comment -

            We could REALLY use this functionality.  Are there any plugins supporting this LIMIT capability?  Looks like the Pigsty tools is not supported any more.

            Bill Tanner added a comment - We could REALLY use this functionality.  Are there any plugins supporting this LIMIT capability?  Looks like the Pigsty tools is not supported any more.

            Raphael Varieras added a comment -

            A LIMIT statement in JQL would definitely be useful, especially with certain plugins.

            Raphael Varieras added a comment - A LIMIT statement in JQL would definitely be useful, especially with certain plugins.

            Fabrice Kurz added a comment -

            This is not only for visualization usefull. For some plugins, we have to limit the issue number to less then 1000... (BigPicture)
            I also dont understand why you are not able to fix this..

            For example i have seen, when you make a bulk change, the data is also limited to 1000 sets.
            So i imagine that you are able to limit the data in the background.

            So why you can't offer the limit function in the foreground?

            Fabrice Kurz added a comment - This is not only for visualization usefull. For some plugins, we have to limit the issue number to less then 1000... (BigPicture) I also dont understand why you are not able to fix this.. For example i have seen, when you make a bulk change, the data is also limited to 1000 sets. So i imagine that you are able to limit the data in the background. So why you can't offer the limit function in the foreground?

            David Vega added a comment -

            I think this is because Hybernate's HQL does not support "LIMIT": http://stackoverflow.com/questions/1239723/how-do-you-do-a-limit-query-in-hql

            David Vega added a comment - I think this is because Hybernate's HQL does not support "LIMIT": http://stackoverflow.com/questions/1239723/how-do-you-do-a-limit-query-in-hql

              Unassigned Unassigned
              bc32e99a92d8 Svante Gustafsson Björkegren
              Votes:
              1 Vote for this issue
              Watchers:
              55 Start watching this issue

                Created:
                Updated:
                Resolved: