Docs

Use Haulcopy

The Marketplace name is Haulcopy: Scheduled Excel, CSV & PDF Export for Jira. Haulcopy is a third-party app. It is not made by Atlassian.

Open it

• Apps → Haulcopy: Scheduled Excel, CSV & PDF Export for Jira opens the global page.
• A project page of the same name starts from project = KEY.
• The issue navigator action is labeled Export with Haulcopy and opens a dialog with the current JQL filled in.

The page has three tabs: Export, Schedules, and History.

Export

1. Check the JQL. Keep it to the issues you mean to export.
2. Choose Excel (.xlsx), CSV, PDF, or any mix.
3. Key is always the first column. It is shown as its own label, not as a field you can remove. Summary, Status, Assignee, Priority, Created, and Updated start selected. Search the list to add fields, up to 50 columns in total.
4. Start the export.

A formatted Excel file has date and number cells, a frozen header, an autofilter, column widths, and a link on the issue key. CSV is the same columns as plain text. PDF is landscape A4, with wrapped text, page numbers, an optional title, and an optional PNG logo under 80 KB. Set the title and logo on the Export tab before you start. A blank title uses the JQL, shortened, as the PDF heading.

The page shows progress while the export runs. If another export is already running on the site, the new one waits. Only one export runs at a time.

A search of more than 10,000 issues is written as separate files of 10,000. History names the parts.

History

Each row shows the JQL, how many issues and fields were written, the format, the size, when it was created, and who ran it. Download each file from the row. The same download appears on the Export tab when that job finishes.

Export files expire after seven days. Download before then. The app cannot rebuild an expired file.

If a row stays queued, use Resume. If a row fails, the error text stays on the row. Start a new export rather than resuming a failed one.

Presets

On Export, name the current JQL, fields, and formats and save them as a preset. Load a preset from the list. Deleting a preset removes it from the list. You can keep 100 presets.

Schedules

On Schedules, add a daily, weekly, or monthly run.

• The clock starts as the timezone on your Jira profile. The time you pick is that zone’s local time.
• Monthly runs use a day from 1 to 28, so the day exists in every month.
• Copy the JQL, fields, and formats from the Export tab, or fill them from a preset, then edit them.
• A check every five minutes starts any schedule that is due. Each schedule runs at most once per local day.
• The search runs as the person who owns the schedule, so issue security and project permissions still apply.
• Finished files appear in History for that owner. The app does not send email, and it does not post a Jira notification.

A site can keep 1,000 schedules. Pause a schedule to skip it without deleting it.

License

On a paid Marketplace install, an active license can export. A site that falls outside the license is told so on the page and cannot start an export. Files are never watermarked.

The intended price is free for a Jira site with up to 10 users, then $1.49 per user per month. Atlassian bills that. Haulcopy does not count users. It follows the license Atlassian reports. A development install has no Marketplace license, and exports are allowed there so the app can be tested. That is not the 10-user free tier.

What the app stores

On your site, inside Atlassian:

• The export files you download, for seven days.
• Job records, presets, schedules, the PDF title, and the PDF logo.

It does not send issue data to the vendor. Details are in the privacy policy.

Permissions

• Read Jira work items, including permission to act as a user. Scheduled and queued exports need that so they search as the schedule owner rather than as the app.
• App storage, for the files and settings above.

It does not ask for permission to call an external service.