Availability: JIRA JIRA SERVICE MANAGEMENT
Category: ESTIMATION
Establish precise control over viewing and editing permissions for custom field values with a focus on confidentiality and restricted access. Assign permissions to specific roles, such as project leads or reporters, members of designated groups (e.g., atlassian-administrators), or specific users, including high-profile individuals like your CEO. This ensures that only authorized personnel can access and modify sensitive information, reinforcing privacy and protection measures. For other users, they can view the overall issue, but the specific field values remain confidential and restricted.
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.
Preview
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
WSJF (Weighted Shortest Job First)Calendar fieldJira Service Management (JSM)
The Multi User Select field is currently not available for Jira Service Management
Data Structure (Automation)
To set the value via automation, you need the following object structure
{
"users": [
{
"accountId": string,
"name": string,
"imageUrl": string
}
]
}