-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
7.13.0, 8.0.0, 8.1.0
-
None
-
7.13
-
5
-
Severity 3 - Minor
-
2
-
Summary
As per JRASERVER-34746, the /rest/api/2/issue/<issueKey>/worklog does not support pagination or ordering
Steps to Reproduce
- Create an issue that has a reasonable number of worklogs
- Attempt to request the worklog endpoint, using the startAt, maxResults, total or orderBy to filter the results. For example, http://localhost:8080/rest/2/api/issue/TEST-1/worklog?maxResults=10.
Expected Results
The rest endpoint returns the results in line with the parameters specified in the URL. In the example given, only 10 results should be returned (and the value should be reflected in the JSON output).
Actual Results
The rest endpoint returns all results, from oldest to newest. The maxResults value in this example would show all worklogs for that issue.
Workaround
Use Automation for Jira to send the webhooks. It does allow to customize the payload using Smart Links.
Reference: How to send a webhook with all worklog entries using Automation for Jira
- is related to
-
JRASERVER-34746 The /rest/api/2/issue/<issueKey> endpoint does not respect pagination parameters
- Gathering Impact
- mentioned in
-
Page Loading...