Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-66159

Issue Exports Should Default to the Max Limit

    XMLWordPrintable

Details

    • Suggestion
    • Status: Gathering Interest (View Workflow)
    • Resolution: Unresolved
    • None
    • None
    • 2
    • 9
    • 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.

    Description

      Recently this was fixed to have exports recognize a limit:

      The problem is that if users simply do a search that returns more than the max limit, they'll hit an error with no details on how to workaround the problem.

      In the past, before JIRA 7, the exports would by default set tempMax to be 1000. But with the new exports, the default does not have a limit, so users will commonly run into the forbidden error.

      With that, issue exports should do the following:

      1. Automatically have the tempMax parameter set as default to match the max limit
      2. Provide instructions on how to change the tempMax limit.

      Example of error:

      Workaround
      1. Append the URL with &tempMax=1000

       Check an example script at https://confluence.atlassian.com/jirakb/exporting-jira-s-issues-using-csv-in-batches-1071829731.html

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              dchan David Chan
              Votes:
              14 Vote for this issue
              Watchers:
              18 Start watching this issue

              Dates

                Created:
                Updated: