Secure Field
The Secure Field allows you to store sensitive information in Jira issues with precise control over who can view and edit the data. This guide explains how to configure and use the Secure Field.
Configuring a Secure Field
When you configure a Secure Field, you'll need to make decisions about the field type and access permissions:
1. Field Type Selection
The first step in configuring your Secure Field is selecting the type of data it will store:
Text: Simple text values (single line)
Number: Numeric values only
Date: Calendar date values
Choose the field type that best matches the sensitive data you need to store.
Once a field type is selected and saved, it cannot be changed within the current context configuration. This is because, for example, if a field is initially configured as a Text field and a string value is stored, switching it to a Date field would lead to incorrect parsing and display issues.
Even if the context configuration is deleted, the custom field value stored in the issue does not get removed. Instead, a type mismatch error will occur if the field is reconfigured with a different type. To make the previously stored value visible again (if you have the necessary permissions), you must reconfigure the field using the original type.
2. View Permissions
The View Permissions section controls who can see the data stored in this field:
Users with view permission: Specific Jira users who can view the field
Groups with view permission: Jira user groups that can view the field
Project roles with view permission: Project roles that can view the field
3. Edit Permissions
The Edit Permissions section controls who can modify the data stored in this field:
Users with edit permission: Specific Jira users who can edit the field
Groups with edit permission: Jira user groups that can edit the field
Project roles with edit permission: Project roles that can edit the field
Users with edit permission are automatically granted view permission as well.