Details
-
Suggestion
-
Resolution: Fixed
Description
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Currently full changelog is returned when using expand=changelog in /search or /issue endpoint. It may cause OOM easily. At least in JIRA Cloud such requests are killed with timeout error, quite often.
It would be much better if only 100 changelog entries were returned by /search or /issue enpoint, and new /issue/{idOrKey}/changelog endpoint would then return full history on request.
Note, this technique is used for worklog currently.
See also https://answers.atlassian.com/questions/316418/iterate-through-changelog-history-with-rest-api and https://bitbucket.org/azhdanov/jiratimesheet/issues/760/timesheet-report-gadget-generates-timeout
Attachments
Issue Links
- is related to
-
JRACLOUD-67458 rest/api/2/search endpoint returns error 500 when expanding the changelog
- Closed
-
JRASERVER-59998 Limit changelog to 20 entries, and add /changelog endpoint for full history
- Gathering Interest
- relates to
-
JRACLOUD-67458 rest/api/2/search endpoint returns error 500 when expanding the changelog
- Closed
-
ACJIRA-1200 Loading...
-
CRANE-825 Loading...
-
JCE-1416 Loading...