This Secure Fields custom field type provides various secure field types. Jira administrators can create numbered, textoffers secure text, number, and date custom fields like Jira standard ones. After defining , similar to standard Jira fields. Admins can set view and edit permissions in the context screen, users without permissions can´t see or edit the hidden information and will get a message that they are not permitted to view or edit.
...
during the creation. Users without permission will see a message indicating they can't view or edit the hidden information.
...
| Tip |
|---|
Secure Fields are available in the JSM portal. For a list of supported fields and setup instructions, please visit Fields in Jira Service Management (JSM) Portal. |
...
Create and configure the custom field
| Note |
|---|
To create and configure the Secure Fields custom field, you must be logged in as a user with Jira Administrator permissions. |
...
Go to Apps → Manage your apps → Fields
Click on Create custom field button on the right side of the screen.
Select Secure Fields and click Next.
Name and add a description to your field then click Next.
Select a field type (Text, Number of Date) and give View/Edit permissions to users, groups, project roles, reporter or assignee, then click Next.
Associate the field to the appropriate screens and click Create. You must associate a field to a screen before it will be displayed
In the issue and create views, users will receive appropriate messaging if they lack view or edit permissions.
In the issue and create views, users will receive appropriate messaging if they lack view or edit permissions.
...
| Note |
|---|
Limitations in Fields Secure Fields In the Issue Navigator (Filters → View all issues), secure fields will not function as intended won’t work as expected due to an Atlassian limitation that ignores bypasses permissions on this screen. To maintain protect privacy and respect view permissions, secure fields are not displayed in the Issue Navigator. Instead, you will see show as "Map of 1 Element" where the secure field would normally appear. View permissions for secure fields are not supported in the Issue Navigator and can only be enforced in all other view screenshere. See more limitations here. |
...