On this page
Field Configuration
Before starting the field configuration, please follow the instructions for creating custom fields
Step 1: Set a name and description
Provide a good name for the new custom field. Make it descriptive, concise, and easy to understand for others who will use it. Avoid using ambiguous or overly technical terms.
Step 2: Setup permissions
During testing, you have the option to "grant access to all users," effectively disabling the feature for broader evaluation.
Alternatively, when opting for "restrict permissions," you can specify roles, individual users, or groups that are exclusively granted the ability to read and write the field value. For all other users, the field value remains obscured, appearing as illegible text and ensuring restricted visibility.
It's important to note that even when access is restricted, the field value can still be set through API or automation by unauthorized users. However, this "readable value" will not be visible in the issue view, maintaining the intended confidentiality and privacy measures.
Field view and edit
Edit view
When a user is granted permission, you can input your secure value. The information box will display the authorized users, roles, or groups that have the capability to read or write that specific value, providing transparent visibility into the permitted access.
Unauthorized users will be unable to edit or view the specified value.
Secret value in issue view
Related Use Cases
More use cases are coming soon. In the meantime, check out our other use cases.
Jira Service Management (JSM)
The Secure field is not available for Jira Service Management
JQL expression
The Secure field should not be used in JQL queries
Data Structure (Automation)
The Secure field is not compatible with automation