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: Does version 3.0.0 work on Jira 10.x?

A: No. Starting with version 3.0.0, the add-on requires Jira Data Center 11.3 LTS (Java 21). If your site is still on Jira 10.x, stay on version 2.5.0 until you upgrade your Jira platform.

Q: Do I need to re-encrypt data or rotate keys when upgrading to version 3.0.0?

A: No. Version 3.0.0 is a platform upgrade; there is no migration of data, keys, permissions, or scopes. Existing 2.5.0 configurations keep working as-is.