We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
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.
Jira Platform CloudProject Type: software

Jira Platform Cloud

Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-59998

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

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      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

            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 Platform Cloud'
            1. Jira Platform Cloud
            2. JRACLOUD-59998

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

            XMLWordPrintable

              • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

                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

                        Unassigned Unassigned
                        0cd5ba84bf22 Andriy Zhdanov
                        Votes:
                        2 Vote for this issue
                        Watchers:
                        3 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            0cd5ba84bf22 Andriy Zhdanov
                            Votes:
                            2 Vote for this issue
                            Watchers:
                            3 Start watching this issue

                              Created:
                              Updated:
                              Resolved: