Skip to main content
Labrador’s CSV exports give you a way to get your audit data into spreadsheets or developer ticketing tools without configuring a live integration. Both formats are available on every plan, including Free, and both are generated instantly from the Export dropdown in your project toolbar. Use the standard CSV when you need flexible raw data, and use the Jira CSV when you want to import issues directly into a Jira project board.

Standard CSV Export

The standard CSV export produces a flat file containing every issue logged across all pages and components in your project. It is designed to be opened in Microsoft Excel, Google Sheets, or any other CSV-compatible tool, and it gives you full flexibility to sort, filter, and reshape the data however your workflow requires. Columns included in the standard CSV: To export a standard CSV:
1

Open your project

Navigate to the project you want to export from.
2

Click Export

Click the Export dropdown in the project toolbar.
3

Select CSV Export

Choose CSV Export from the dropdown menu. The file downloads immediately.

Jira-Ready CSV Export

The Jira CSV export contains the same issue data as the standard CSV, but the columns are restructured and labelled to match the fields that Jira’s CSV import tool expects. Severity levels are automatically mapped to Jira priority values, so you do not need to manually reformat the file before importing it. How Labrador severity maps to Jira priority: To export and import a Jira CSV:
1

Export from Labrador

In your project, click ExportJira CSV Export. The file downloads immediately.
2

Open your Jira project

Navigate to the Jira project where you want to create the issues.
3

Open the import tool

Click … (More) in the project sidebar, then select Import issues.
4

Choose CSV as the import source

Select CSV from the list of import formats.
5

Upload the file

Upload the Jira CSV file you downloaded from Labrador and follow the Jira import wizard to complete the import.
Jira’s CSV import wizard lets you review the column-to-field mapping before finalising the import. The Labrador Jira CSV is pre-formatted to match standard Jira field names, so most columns should map automatically, but always review the mapping screen before confirming.

CSV vs Live Jira Integration

Both CSV exports and the live Jira integration get your issues into Jira, but they serve different workflows. Use this guide to choose the right approach for your situation.

Jira-Ready CSV

Best for: One-time handoffs, projects where you do not need ongoing sync, or when you are on the Free plan.Export the CSV at the end of your audit and import it into Jira as a batch. Once imported, the issues live in Jira independently, there is no connection back to Labrador, so status changes in Jira do not update Labrador and vice versa.

Live Jira Integration

Best for: Active remediation cycles where you want automatic issue creation and two-way status and priority sync throughout the process.New issues you log in Labrador are pushed to your Jira board automatically. Status and priority changes flow in both directions, close a ticket in Jira and it updates in Labrador too. Available on Core, Plus, and Enterprise plans. See Jira Integration to set it up.
Both the standard CSV and the Jira-ready CSV are available on all plans, including Free. The live Jira sync integration, with automatic issue creation and two-way status updates, requires a Core, Plus, or Enterprise subscription.