Skip to main content

Bulk ZIP export

Create one PDF, Word (DOCX) or Markdown file per Jira issue and download the results as a single ZIP archive. Available in Free and Standard.

Where it is available​

Choose One file per issue (ZIP) in any multi-issue export — JQL search, boards, backlogs, sprints and releases. Single-issue exports keep their normal direct download and do not offer the option. Exportelier remembers the output mode per template in the current browser.

Exportelier Automation can also produce ZIP archives for scheduled JQL exports. A schedule targeting one explicit issue always produces a regular single document.

Creating an archive​

  1. Open a multi-issue export dialog and choose a template and format.
  2. Select One file per issue (ZIP). The dialog shows an estimated file count; the background job re-checks the current Jira result when it starts.
  3. Optionally group files into folders by Project or Issue type. The default is no folders.
  4. Start the export. ZIP exports always run as background jobs and report per-issue progress.
  5. Download the archive when the job completes.

Each entry starts with its issue key, so ordinary ZIP viewers sort the files usefully. Unicode summaries are preserved where the file system allows it; unsafe path characters and invisible directional controls are removed.

Completed with errors​

A failure on a single issue — loading, rendering or signing — does not discard the rest of the run. That issue receives a short *-export-error-*.txt entry containing no stack traces or internal paths, and the job continues. The result is labelled Completed with errors and reports how many issues succeeded and failed.

Failures affecting the whole job — an invalid template, cancellation, a storage failure or the archive size ceiling — never publish a partial download.

Limits and delivery​

  • An archive is limited to 100 MiB and 65,535 entries. Exportelier stops cleanly before either limit and never publishes a truncated archive.
  • A finalized ZIP counts as one export regardless of its issue count. A job that fails before finalization does not count.
  • Scheduled email attachments have a 14 MiB raw-data limit, leaving room for base64 and MIME overhead inside the provider's 20 MB ceiling.
  • Scheduled Jira attachments respect the attachment setting and upload limit reported by the current Jira site. No upload starts when attachments are disabled or the archive is too large.
  • Scheduled webhooks receive artifact metadata only, never ZIP bytes.

See Limits & quotas for the complete reference.