Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-78650

Pagination and query on assignable search REST API

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • REST API
    • None
    • 0
    • 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.

      Hello,

      It was quite confusing to find out that the Jira Server REST API endpoint for users search /rest/api/2/user/search does not have any pagination. I think it will be helpful to add pagination properties for cases when search result returns more than 1,000 users. This will allow to collect results in a proper way without sending unnecessary queries back to the server.

            [JRASERVER-78650] Pagination and query on assignable search REST API

            Andreas Wittich added a comment - - edited

            Sorry. I can not change the description...

            this issue is about the REST command:

            /rest/api/2/user/assignable/search?issueKey=" & sIssueKey & "&query=" & sQuery & "&startAt=0&maxResults=1000".

            Issues:

            • Max results cant be more than 100. Everything above returns 100 first entries only.
            • startAt is completely ignored the 100 elements start always with the 0 one... So it is not possible to get users with higher index that 100...
            • sQuery string is ignored and only the first alphabetical entries are returned.

            Description is available here:

            [The Jira Cloud platform REST API

            As workaround I'm using the command:

            "/rest/api/2/user/picker?query=" & sQuery & "&startAt=0&maxResults=1000"

            which is working fine, but list all filtered users without assignability dependency.

            Andreas Wittich added a comment - - edited Sorry. I can not change the description... this issue is about the REST command: /rest/api/2/user/assignable/search? issueKey=" & sIssueKey & "&query=" & sQuery & "&startAt=0&maxResults=1000". Issues: Max results cant be more than 100. Everything above returns 100 first entries only. startAt is completely ignored the 100 elements start always with the 0 one... So it is not possible to get users with higher index that 100... sQuery string is ignored and only the first alphabetical entries are returned. Description is available here: [The Jira Cloud platform REST API As workaround I'm using the command: "/rest/api/2/user/picker?query=" & sQuery & "&startAt=0&maxResults=1000" which is working fine, but list all filtered users without assignability dependency.

              Unassigned Unassigned
              9189da551e19 Andreas Wittich
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: