The following table describes the four levels of access for a field:
Permission
Meaning
None
The field will not be visible to the user on the My Issues list or the Issue Details page. The layout designer, filter wizard and advanced filter page will not show the field in the list of available fields. An exception is the Project field. This field can be set to ‘Inquiry’ or ‘Update’ only – ‘None’ is not an available option.
For site administrators this setting is ignored. A site administrator can always update any field.
Inquiry
The field will be visible to the user on the My Issues list and the Issue Details page, but the contents of the field cannot be updated. The layout designer, filter wizard and advanced filter page will show the field. The Issue Details page will show the field, but the field will be disabled. For site administrators this setting is ignored. A site administrator always can update any field.
Update Assigned To
The field will be visible and can be updated by the user if the issue is assigned to the user. If the issue is not assigned to the user the field is visible but cannot be updated. For site administrators this setting is ignored.
Update Any
The field will be visible and can be updated by any user that has access to the issue regardless of who the issue is assigned to.
IMPORTANT CONSIDERATIONS FOR FIELD LEVEL SECURITY:
If a user’s group membership restricts them from viewing certain fields, they will not be able to access full history details as that would allow them to view restricted fields.
If a user creates a filter that uses a field that they have access to and then at a later time access is denied, they will still have that filter. They will not be able to view the fields but may be able to intuit the value of the field based on the filter results.
All users can create advanced filters. Advanced filters do not restrict access to fields. A user could create advanced filters that would allow them to intuit field values.
If a user that has access to a field creates a filter that uses that field and publishes the filter to all users, all users will be able to use that filter and may be able to intuit the field values.
Workflow rules that designate fields as required will be ignored if the user does not have update access to the required field(s).
E-Mail notification templates that contain imbedded issue fields that some users do not have access to, will still be received by designated recipients and the restricted fields will appear in the e-mail.