Feature spotlight
In This Blog
Secured field values don’t come along with Jira’s standard CSV export, the encryption that keeps them safe on the issue view keeps them out of a normal export too. That’s the right default, but it leaves a gap for anyone who has a legitimate, permitted reason to analyze that data outside Jira: a monthly reporting cycle, a spreadsheet pivot table, a one-off audit request.
Secure Custom Fields for Jira has its own CSV export built for exactly that gap.
From the app, a user with the right permissions picks which issues and which fields to include (secured and standard Jira fields together) and exports up to 1,000 issues at a time to a CSV file. If someone without view permission ends up looking at that export, restricted values show as “****” rather than the real data, so the export respects the same permissions as the issue view.
The field selection can also be saved as a reusable state, so a recurring report doesn’t mean rebuilding the field list from scratch every time.
Picture an ops lead who runs the same compensation-data report for finance on the first of every month: the same dozen fields, the same issue filter, every time. The first export takes a few minutes to set up and select fields. After saving that selection, every report after that is one click: load the saved state, hit export, done.
For the full steps, including how saved exports work, see Export field values to a CSV file.
Not using Secure Custom Fields for Jira yet? Start a 30-day free trial to see how reporting works on secured data.