Frequently Asked Questions (FAQ)

Q: How can I automatically grant permission to the assignee of an issue to view an encrypted field?

A: As of version 1.1.0, you can do this by editing the field's configuration and selecting the Assignee option in the Jira Fields field. This is part of the new dynamic permissions functionality. You can also do the same for the Reporter.

Q: What happens if I refresh the page after revealing a field's value?

A: The field's value will revert to its default encrypted state (*******). The data display is temporary and only lasts as long as you stay on the page without refreshing it.

Q: If I reveal a field's value, can other users see it?

A: No. The action of showing the value is personal and only affects your current view. Other users will continue to see the encrypted value until they reveal it themselves and have the necessary permissions.

Q: What happens if a user tries to view a field for which they do not have permissions?

A: When attempting to reveal the value, the field will display the message [NO ACCESS], explicitly indicating that they are not authorized to view that information.

Q: Can issues be searched using the value of an encrypted field in JQL?

A: No. Due to the nature of encryption, the content of Secure Fortress fields cannot be indexed by Jira for JQL searches.

Q: What is a field context and what is per-context configuration for?

A: In Jira, a context defines which projects and issue types a custom field is available in. Starting with version 2.4.0, you can configure permissions and scope independently for each context — for example, restricting access in an "HR" context while allowing all authenticated users in another. See per-context configuration for details.

Q: What happens when a context has no configuration of its own?

A: It automatically inherits the global configuration of the field. The UI displays the "Inheriting the global configuration" indicator in both the permissions and scope sections. Global configuration is managed from the field's ··· → Secure Fortress menu. See the inheritance model for the full explanation.

Q: How do I remove a context-specific configuration and return to the global one?

A: On the Jira Admin → Custom Fields → Configure screen, open the desired context and click "Reset to global" in the permissions or scope section you want to revert (each section resets independently). After confirming, the context returns to inheriting the global configuration. See Reset to global configuration.