Import Values into Protected Custom Fields
Use the import feature to copy values from standard Jira fields, or from a CSV file, into secure fields created by Protected Custom Fields.
Imported values are encrypted and can only be revealed by users in the groups assigned to the destination field.
The import copies values. It does not remove the values from the source field. See After the import.
Before you start
Update the app. The import feature is part of a major version update, so you must approve it manually. In Jira, go to Settings → Apps → Manage apps, select Protected Custom Fields, and approve the update. Until you approve it, the import options do not appear.
Create the destination fields. Each value you want to protect needs a protected field to go into. Protected Custom Fields supports Number, Text (single line) and Text (multi line). Create a protected field of the same type as the source field. See Create a protected custom field.
Assign permission groups. New protected fields have no groups assigned, so nobody can see the imported values until you add at least one Jira group. See Set Permission Groups for Protected Custom Fields.
Check the source field type. You cannot import from field types the app does not support, such as checkboxes. You cannot use an existing protected field as a source.
Import from Jira Fields
- Open Protected Custom Fields from Jira settings and select the Import tab.
- Select Import from Jira fields.
- Select the space that holds the source fields and data.
- In the list of fields, use the dropdown next to each source field to choose its destination protected field. Leave fields you do not want to import unmapped.
- Select Next to open the preview. Check the sample values and their destination fields. The preview identifies work items by their numeric issue ID.
- Select Start import.
- When the import completes, select Done.
Each protected field can be the destination for one source field only. Once you select it in one dropdown, it is removed from the others. Clear the mapping to make it available again.
Import from a CSV
Use this option when the values are not in your Jira Cloud site yet, for example after a migration or when a team has kept values in a spreadsheet.
Prepare the File
The importer matches rows to work items by issue ID and reads custom-field columns by their Jira export header.
The file must include:
An Issue ID column containing the numeric ID of each work item on this site. A file that contains only issue keys is rejected.
One column per value you want to import, with the header in Jira's export format: Custom field (Field name).
The simplest way to get this format is to export the work items from Jira. In the work item search, choose Export → CSV (All fields), then add or edit the columns you want to import.
Run the Import
Open Protected Custom Fields from Jira settings and select the Import tab.
Select Import from CSV and upload the file.
Use the dropdown next to each column to choose its protected destination field. Leave columns you do not want to import unmapped.
Select Next and check the preview.
Select Start import.
When the import completes, select Done.
Check the Import
Open a work item that was included in the import.
As a user in an assigned permission group, select the eye icon on the protected field and confirm the value is correct.
As a user outside those groups, confirm the work item opens as normal and the protected value cannot be revealed.
After the Import
The source field and its values stay in place. Anyone who can open the work item can still read them until you clear or delete the field.
Before you change the source field, check what else depends on it: automation rules, filters, dashboards, reports, exports and integrations. Then either clear the sensitive values, edit them out if the field also holds information the wider team needs, or delete the field.
Clearing or deleting the field does not remove values from work item history, backups or earlier exports.