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

Limit changelog to 20 entries, and add /changelog endpoint for full history

XMLWordPrintable

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

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? 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 20 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

              Unassigned Unassigned
              0cd5ba84bf22 Andriy Zhdanov
              Votes:
              23 Vote for this issue
              Watchers:
              30 Start watching this issue

                Created:
                Updated: