Changelog

Release 3.0.0

Platform major release. Upgrades Jira Secure Fortress compatibility to Jira Data Center 11.3 LTS, which requires Java 21. It does not include new functionality: field administration (Fields, Keys, Migration, Logs), encrypted fields, permissions, per-context scope, and inline reveal work exactly as they did in 2.5.0.

• Jira Data Center 11.3 LTS compatibility: The add-on is validated and runs on Jira Data Center 11.3 LTS, which requires Java 21.
• No product changes compared to 2.5.0: Global and per-context configuration, scope filtering to the projects and issue types of the context, global → context inheritance, the official logo, and the eye icon remain unchanged.

Compatibility: If your Jira site is still on version 10.x, stay on version 2.5.0 of the add-on; 3.0.0 cannot be installed on Jira 10.x. If your site is already on Jira Data Center 11.3, upgrade through the standard .jar process via UPM: there is no migration of keys, permissions, or configured scopes.

Release 2.5.0

Release focused on completing the per-context configuration model introduced in 2.4.0. Closes the known protection scope limitation, adds context visibility to the dashboard and the dedicated field page, and publishes the redesigned official logo.

• Protection scope filtered by Jira context: When editing the protection scope in a specific context, the project and issue type selector now shows only the projects and issue types that belong to that context. It is not possible to save configurations with projects or issue types outside the context bounds. Leaving the selector empty applies protection to all projects and issue types in that context, not across the entire instance. In the global configuration, the selector retains the full instance catalog (previous behavior unchanged).
• "Configure contexts" link on the dedicated page: The field's dedicated page (accessible from the ··· → Secure Fortress menu) now includes a direct link to the native context configuration screen. Help text makes clear that the global configuration is managed from the dedicated page, while per-context configuration is handled from the native Jira screen.
• Context view in the admin dashboard: Each field in the Fields section of the dashboard now shows an expandable row listing its Jira contexts. Each context includes status indicators showing whether permissions and scope are configured independently for that context or inheriting the global configuration. The Global row remains editable from the dashboard modal; context rows are read-only and include a direct link to the field configuration screen for that context.
• Redesigned official logo: The add-on debuts its new official logo, designed following the mobile app icon style standard.

Compatibility: Standard .jar upgrade via UPM; existing 2.4.0 configurations continue to work without manual migration. Review per-context scopes configured in previous versions that may have included projects or issue types outside the context bounds, as from 2.5.0 those selections are excluded by the new filtering.

Release 2.4.0

Release focused on granular per-context configuration. Encrypted fields with multiple Jira contexts can now have different access permissions and protection scope in each one, with automatic inheritance from the global configuration when a context has no override of its own.

• Per-context configuration in the native Custom Fields screen: The Jira Admin → Custom Fields → Configure screen now displays the Secure Fortress – Permissions & Scope panel once per field context. Each context can be configured independently without affecting the others.
• Global → context inheritance model: The global configuration acts as a fallback for contexts without their own override. The UI shows "Inheriting the global configuration" for each context that has no override. The "Reset to global" button removes a context override and restores automatic inheritance.
• Extended permission mode: New "Who can decrypt this field?" selector with two options: All authenticated users (any logged-in Jira user can decrypt the field) or Specific users, groups, roles (an explicit list of users, Jira groups, issue roles, and project roles).
• Global dedicated page: The page accessible from the field's ··· menu (Secure Fortress option) remains available for editing the global field configuration, without a context selector.
• Backward compatibility: Existing configurations from previous versions (2.1.0–2.3.0) continue to work without manual migration.

Limitation resolved in 2.5.0 — Protection scope per context: Protection scope inheritance per context is supported in this version. Independent scope filtering per context (restricting encryption to projects and issue types within the context bounds) is available starting with release 2.5.0.

Release 2.3.0

Release focused on the native administration experience. Administrators can now manage access permissions and the protection scope of each encrypted field directly from the standard Jira workflow, without having to navigate to the plugin administration panel.

• Native permissions and scope management from Custom Fields: New Secure Fortress entry in the ··· menu of each encrypted field in Jira Admin → Custom Fields, opening a dedicated configuration page with two sections: Access permissions (users, groups, issue roles, and project roles) and Protection scope (global, by project, or by issue type).
• Edit modals with multi-select pickers: User, group, and role selectors with full support for Jira DC dark mode.
• Support for all encrypted field types: The native page is available for Encrypted Custom Field, Encrypted Text Area, and Encrypted Number.
• Backward compatibility: The plugin administration panel remains available; both access paths share the same configuration without interference.

Limitation resolved in 2.4.0: In this version, the configuration applied to all contexts of the field. Per-context configuration is available starting with release 2.4.0.

Release 2.2.0

Release focused on improving the usability of encrypted-field access. It introduces an eye icon directly on every encrypted field in the issue detail view, letting authorized users decrypt and re-mask the value inline with a single click — synchronized with the existing modal and compatible with dark mode.

Release 2.1.0

• Protection scope by project or issue type: When configuring an encrypted field, administrators can now choose whether the protection applies Globally, only to selected Projects, or only to specific Issue types. This helps reduce unnecessary encryption in non-sensitive projects. The configured scope is clearly displayed in the administration panel.

Release 2.0.0

• Historical encryption when protecting existing fields: When converting a standard text field to an encrypted field, the add-on automatically encrypts all previous field values in the background, without interrupting the team's work.
• Encryption key rotation: Administrators can now rotate the encryption key of any field directly from the administration panel. The process runs in the background and authorized users maintain access to data throughout the entire operation.
• Field protection revocation: New option to disable the protection of an encrypted field and return it to plain text, automatically removing all its viewing permissions.
• Reference images in the field type selector: The field type selector now displays preview images for the "Encrypted Text Area" and "Encrypted Number" types, making them easier to identify when creating new fields.

Release 1.1.2

This update resolves issues detected when deploying the add-on in real production environments, ensuring that all administration and user tools work correctly and stably.

• Jira 10.3 Compatibility: The add-on is now fully optimized for Jira Data Center v10.3 and works without issues in multi-server (node) configurations.
• Admin Panel Improvements: Fixed an issue that prevented using the buttons in the configuration panel, allowing administrative adjustments to be made normally.
• Audit Log Correction: Solved the error message that interrupted the display of system logs.
• Multi-language Support: The application is now fully available in English, with all its labels and messages correctly translated.
• Issue View: Repaired the button to view protected data (decrypt) in tickets, which previously displayed an error when attempting to use it.

Release 1.1.1

Important: Immediate update to this version is highly recommended to prevent data integrity issues.

• Critical Data Loss Fix: Resolved a severe bug in the Secure Fortress add-on that caused data loss when managing multiple fields within the same issue.
  • The Issue: Previously, editing a single encrypted field in a ticket containing multiple add-on fields caused the remaining fields to reset or lose their stored values.
  • The Solution: Data persistence is now guaranteed across all fields in an issue, regardless of which individual field is being edited.

Release 1.1.0

• Added dynamic viewing permission option for Assignee and Reporter.
• Incorporated a new panel for viewing encryption keys and their mapping to fields.
• Improved the audit log to record data access and administrative actions.
• Added filters for date, user, action, and others in the log view.
• Fixed a security vulnerability that exposed decrypted values in the logs.
• Fixed a minor project compilation issue.

Release 1.0.0

• Initial release of Jira Secure Fortress.
• Creation of "Encrypted Custom Field" type fields.
• Administration dashboard to manage fields and permissions.
• Assignment of viewing permissions to groups and users.
• Mechanism to show/hide values in the issue view.
• Audit logs (Logs) section with TXT export.