IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-34746

The /rest/api/2/issue/<issueKey> endpoint does not respect pagination parameters

XMLWordPrintable

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

      Summary

      When querying the rest/api/2/issue/issueKey endpoint, the worklog properly only includes the first twenty results - and this property does not support the usage of expansion or pagination, as outlined in the REST API platform page documentation.

      Steps to Reproduce

      1. Create an issue with several worklog entries.
      2. Browse to http://localhost:8080/rest/api/2/issue/TEST-1?expand=worklog&maxResults=40

      Expected Results

      The rest endpoint should return at most 40 results in the worklog section.

      Actual Results

      The REST endpoint only returns the first 20 results in chronological order.

      Workaround

      Use the /rest/api/2/issue/<issueKey>/worklog endpoint to list all worklogs for a given issue. Additional manipulation will be required by the REST consumer to sort or filter those results; as that endpoint does not support pagination either. Please see JRASERVER-69308 for more details.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Data Center'
            1. Jira Data Center
            2. JRASERVER-34746

            The /rest/api/2/issue/<issueKey> endpoint does not respect pagination parameters

            XMLWordPrintable

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

                Summary

                When querying the rest/api/2/issue/issueKey endpoint, the worklog properly only includes the first twenty results - and this property does not support the usage of expansion or pagination, as outlined in the REST API platform page documentation.

                Steps to Reproduce

                1. Create an issue with several worklog entries.
                2. Browse to http://localhost:8080/rest/api/2/issue/TEST-1?expand=worklog&maxResults=40

                Expected Results

                The rest endpoint should return at most 40 results in the worklog section.

                Actual Results

                The REST endpoint only returns the first 20 results in chronological order.

                Workaround

                Use the /rest/api/2/issue/<issueKey>/worklog endpoint to list all worklogs for a given issue. Additional manipulation will be required by the REST consumer to sort or filter those results; as that endpoint does not support pagination either. Please see JRASERVER-69308 for more details.

                        Unassigned Unassigned
                        d403d295adf5 Talk About
                        Votes:
                        128 Vote for this issue
                        Watchers:
                        106 Start watching this issue

                          Created:
                          Updated:

                            Unassigned Unassigned
                            d403d295adf5 Talk About
                            Affected customers:
                            128 This affects my team
                            Watchers:
                            106 Start watching this issue

                              Created:
                              Updated: