Changelog

Release 1.9.0 · Forge 7.0.0

Minor release on top of 1.8.0: JQL functions to search work items by colour in Traffic Light KPI and Percentage Field, a new attachment count validator, and two Attachment Field fixes (saving several files and downloading from the preview). The app moves to Forge 7.0.0 because it adds new permissions.

✨ New Features:

• JQL search by colour band: Two new JQL functions, trafficLightBand and percentageBand, find the work items whose field is red, yellow, or green according to the thresholds of their context, without repeating those thresholds in the query. They work in work item search, saved filters, dashboard gadgets, and JSM queues. For example: issue in trafficLightBand("red"). A second argument narrows the search to one field. The field's numeric operators don't change, and neither does the indicator or the bar. See Colour band properties.
• "Attachment Count" validator: New workflow validator that blocks the transition when an Attachment Field has fewer or more files than configured. It supports one or more fields, with a minimum, a maximum, or both per field, and an optional error message. Files added on the transition screen are counted too. See the Attachment Count Validator guide.
• Download from the preview: The Attachment Field preview window (images and text files) now has a Download button next to Close. The file card still shows a single action. Same behaviour on the work item view and the JSM portal. See the User Guide — Attachment Field.

🐞 Fixes:

• Several files in the Attachment Field: The field now saves every file up to the maximum configured for the context, whatever the file name length, when creating, editing, or transitioning a work item. Before, uploading two or more files while creating a work item could raise a length error and block the creation, or the field could save fewer files than uploaded.
• Maximum files per context: The Maximum files setting now accepts values from 1 to 7. If a context had a higher value saved, 7 applies and the context configuration shows a warning until it is saved again.

📝 Technical Notes:

• New permissions: Forge 7.0.0 adds permissions to keep colour searches up to date (read:app-data:jira, write:app-data:jira) and a temporary storage for the Attachment Field (storage:app). Atlassian will ask the site administrator to approve the update from Apps → Manage apps. See the Installation Guide.
• Upgrade path from 1.8.0 (Forge 6.1.0 → 7.0.0). No data migration. The context restrictions, native attachments, and card view from 1.8.0 are kept.

---

Release 1.8.0 · Forge 6.1.0

Minor release on top of 1.7.0: the Attachment Field changes its storage and its view. New files are stored as native Jira attachments and displayed as cards (thumbnail or icon), on both the JSM portal and the agent view.

✨ New Features:

• Native Jira attachments: Files uploaded through the Attachment Field from this version onward are created as native attachments of the work item. The field only stores the identifiers of the files that belong to it; preview and download are served directly from those native attachments. Deleting a file from the field permanently deletes the native attachment. If the app is uninstalled, the files remain in Jira. Context restrictions (maximum file count, types, extensions, size) do not change. See the Attachment Field Admin Guide.
• Card view on portal and agent view: Each file is now displayed as a card with a thumbnail (JPG, PNG, GIF, WEBP images) or type icon (PDF, Word, Excel, and other documents), name, type, and size, and a preview icon (if a preview is available) or a download icon (if not). Multiple files are shown stacked. SVG files and other formats that are not safe to preview inline always use an icon and download. See the Attachment Field User Guide.

⚠️ No migration of previous files:

• Files uploaded before this update are not automatically migrated to the new storage: they remain in the storage used by version 1.7.0, and the field continues to display them normally. A work item updated from 1.7.0 may end up with a mix of older and newer files within the same field. Older files do not appear in the native Attachments panel or in attachments is not EMPTY, and do not survive an app uninstall on their own.
• As of this version, the JQL query attachments is not EMPTY does detect the Attachment Field's new files (because they are native attachments), but does not let you tell which field they came from; for that, keep using "Field name" is not EMPTY.

📝 Technical Notes:

• Standard upgrade path from 1.7.0 (Forge 6.0.0 → 6.1.0). No data migration for previous Attachment Field versions.
• Attachment Field context restrictions and every other module (including the Workflow Expression Condition) are unchanged in this release.

---

Release 1.7.0 · Forge 6.0.0

Functionality release with two new modules: the Attachment Field and the Workflow Expression Condition. This version requires updating the installation and re-consenting from Apps → Manage apps.

✨ New Features:

• Attachment Field: New custom field type to associate files directly with a specific work item field — for example, Invoices, Evidence Photos, or PQR Documents — independently of Jira's native attachments panel. Supports per-context configuration of maximum file count, allowed file types, custom extensions, and maximum file size. Available on the work item view, create, edit, transition screens, and the JSM portal. Supports JQL using is EMPTY / is not EMPTY. See the Attachment Field Admin Guide and the Attachment Field User Guide.

• Workflow Expression Condition: New workflow transition condition that hides the transition button when the work item does not meet a Jira expression defined by the administrator. Unlike validators, which block the transition after the user attempts it, this condition prevents the button from appearing at all if the work item does not meet the criterion. Available only in company-managed spaces. See the Expression Condition Guide.

⚠️ Important Limitations:

• The Attachment Field does not replace Jira's native attachments: files stored in the field do not appear in the work item's Attachments panel and are not detected by attachments is not EMPTY.
• The Attachment Field uses Forge Object Store (Preview): deleting a file from the field removes the object from the store; deleting the work item does not automatically clean the Object Store.
• The Workflow Condition evaluates Jira expressions, not classic JQL. History operators such as WAS or CHANGED are not supported.
• The workflow condition module is in Preview status on the Atlassian Forge platform.
• The Workflow Condition is available only in company-managed spaces.

📝 Technical Notes:

• Mandatory upgrade: This version introduces a major Forge version change (from 5.x to 6.0.0). After deployment, the site administrator must update the installation from Apps → Manage apps and re-consent to the new permissions.
• Compatible with all existing field and validator configurations from version 1.6.0. New modules are configured from scratch.

---

Release 1.6.0 · Forge 5.2.0

Security release: strengthens authorisation on the workflow validator configuration screen and remediates CRITICAL and HIGH+ dependencies detected by the vulnerability scanner integrated into the pipeline.

🛡️ Security:

• Authorisation on validator configuration: The configuration screen for Fields Required and Field Dependency now verifies that the user has administration permissions before loading Jira's field catalogue, contexts, and option lists. An authenticated user without administrator permissions receives an access-denied response when attempting to query this information. Administrators configuring validators experience no change in their usual workflow. The vulnerability impact was read-only (information disclosure); there was no risk of data modification or changes to existing configuration.

• CRITICAL dependency remediation — shell-quote and websocket-driver: Two build-process dependencies with critical severity are updated to secure versions. Neither affects the behaviour of custom fields or workflow validators; no functional changes for administrators or end users.

• HIGH+ dependency remediation — batch of transitive dependencies: A set of transitive tooling dependencies with HIGH+ severity findings from the pipeline's OSV scanner are updated to patched versions (including: tar-fs, undici, ws, node-forge, serialize-javascript, and others). These dependencies are internal to the build process and do not expose user data or change the add-on's behaviour. No functional changes.

📝 Technical Notes:

• No changes to app permissions or manifest: this update does not require re-consent for new scopes.
• Upgrade path: standard Forge version deployment from the Manage apps screen in Jira. Compatible with all existing 1.5.0 configurations; no data migration required.
• Recommended security upgrade: Upgrading to 1.6.0 from any previous version is recommended to meet Marketplace security standards.

References:

Package	Advisory	Severity
shell-quote	GHSA-w7jw-789q-3m8p	CRITICAL
websocket-driver	GHSA-xv26-6w52-cph6	CRITICAL

Security policy: Security Policy — Admin Essentials for Jira

---

Release 1.5.0 · Forge 5.1.0

Mixed release of features, visual identity, and security: the Fields Required validator now supports Cascading Select fields, the add-on's new official logo is introduced, and a CRLF vulnerability reported by Snyk is resolved.

New Features:

• Fields Required validator — Cascading Select support: Cascading Select fields now appear in the validator's Available list and can be added as required. The validator checks that the field has any value selected (parent option chosen); it does not validate a specific value or a specific parent/child combination. See the Fields Required Validator guide for details and limitations.

Visual Identity:

• New official add-on logo: The Admin Essentials for Jira logo is updated with a new design in the standard mobile app icon format, aligned with the suite's visual identity. Visible on Jira's application management screen and in the documentation portal.

Security:

• undici dependency remediation (SNYK-JS-UNDICI-17372658): The undici dependency in the Fields Required Custom UI is updated to close a CRLF Injection vulnerability (severity: Critical). This dependency is internal to the Custom UI build process and does not expose user data. No functional changes for administrators or end users.

Technical Notes:

• No changes to app permissions or manifest: this update does not require running forge install --upgrade for new scopes.
• Upgrade path: standard Forge version deployment from the Manage apps screen in Jira. Compatible with all existing 5.0.0 configurations; no data migration required.

Release 1.4.0 · Forge 5.0.0

New Features:

• Colour band work item properties: Traffic Light KPI and Percentage Field now automatically sync their colour band (🔴 red / 🟡 yellow / 🟢 green) as a Jira work item property. This allows workflow validators, Jira Automation rules, and external integrations to query the current colour without needing to know the numeric thresholds of each context. See Colour Band Properties for keys, usage examples, and limitations.
• Colour operators in Field Dependency: The validator now includes is and is not operators for Traffic Light KPI and Percentage Field. You can now create rules like "if the traffic light is red → require Assignee" directly by colour, without entering numeric thresholds. Existing numeric operators (=, !=, <, etc.) continue to work unchanged. See the Field Dependency Validator guide for step-by-step examples.
• Spanish localisation (es-ES): The entire add-on UI is shown in Spanish when the Jira site or user profile uses the es-ES locale. This includes custom fields, workflow validators, and licensing messages. See Languages and Locales.

Known Limitations:

• No free JQL search by colour: It is not possible to filter work items by colour band using free JQL. As a workaround, use the field's numeric operators with the context thresholds (for example, "My Traffic Light" <= 30 for red). More detail in Colour Band Properties.
• No automatic backfill: Issues created before upgrading to v5.0.0 do not get the colour property until a field on the work item is modified after the upgrade. This can be accelerated with a Jira Automation bulk-update rule.
• Threshold changes are not retroactive: If an administrator modifies field thresholds, the colour property on existing work items only recalculates the next time each work item is saved.

Release 1.3.1 · Forge 4.2.0

Security & Stability:

• lodash dependency update (CVE-2026-4800): This release updates the lodash library to 4.18.1 to remediate a vulnerability reported by the Atlassian Marketplace dependency scanner (EcoScanner). The vulnerability affects older versions present transitively in the Forge ecosystem; Admin Essentials for Jira does not use lodash directly nor expose this functionality in normal app usage.
• No functional changes: Custom fields, workflow validators, and licensing behavior are identical to version 4.0.0.
• Recommended upgrade: If your site is on version 4.0.0, we recommend upgrading to 4.2.0 to meet Marketplace security requirements. No reinstallation or new permissions are required.

References:

• CVE: CVE-2026-4800
• GHSA: GHSA-r5fr-rjxr-66jc
• Security policy: Security Policy — Admin Essentials for Jira

Release 1.3.0 · Forge 4.0.0

New Features:

• Atlassian Marketplace licensing: The add-on is now a paid Marketplace product. Editing fields, configuring thresholds and contexts, and creating or modifying workflow validators require an active license or free trial period.
• Existing data always visible: Without a license, values already stored on work items remain visible on the work item view with an informational notice.
• Clear user messaging: When the license is inactive, the app shows License required and directs users to contact their Jira administrator to purchase or renew.
• New licensing guide: See Atlassian Marketplace Licensing for screen-by-screen and license-state detail.

Known Limitations:

• Workflow validators already configured may keep applying on transitions even after the license expires due to a Jira platform limitation. See the FAQ and the licensing guide for more detail.
• The license covers the full application; there is no per-module licensing.

Release 1.2.0 · Forge 3.1.0

New Features

• Phone Number Field — Country selector:

  • New structured entry UI: country selector (searchable, ~250 ISO 3166-1 entries) + local number field, in an inline layout.
  • Default country per context (contextConfig): administrators can pin a default country per space or work type from the field's context configuration screen.
  • On work item create with an empty field, the context country is pre-selected; on edit, the add-on splits the stored value into country and local number automatically.
  • Updated rendering: 📱 PE +51 943 824 375 with a clickable tel: link.
  • Validation extended to 25 characters max (previously 20).

• Field Dependency Validator — Numeric and text triggers:

  • New trigger fields: Currency, Percentage, and Traffic Light KPI (numeric mode); Email and Phone Number (string mode).
  • Numeric mode: operators =, !=, <, <=, >, >= with a free numeric threshold.
  • String mode: operators equals, does not equal, contains, is empty, is not empty.
  • Rules configured in v3.0.0 continue working without manual reconfiguration.

Release 1.1.0 · Forge 3.0.0

New Features — Custom Fields

• Phone Number Field:

  • New custom field type for storing a single phone number per work item.
  • Format validation consistent on client and server: accepts E.164 (+51 999 888 777), local formats with separators (999-888-777, (01) 234-5678), with total length between 7 and 20 characters.
  • Rendering as a clickable tel: link, with the mobile icon, ready to open the device dialer.
  • Supports inline editing from the work item view, create / edit / transition screens, and the JSM portal.
  • JQL search with exact-match operators.

• Currency Field:

  • New numeric field type that stores a monetary amount and renders it with a configurable symbol (e.g. S/, $, €), position (prefix or suffix) and decimals (0, 2 or 4).
  • Configuration per field context: different spaces or work types can carry different currencies without duplicating the field.
  • JQL still operates on the stored numeric value, not the formatted string.
  • When a context has no saved configuration, the value renders as a plain number using the user's locale.

• Percentage Field:

  • New numeric field type restricted to the 0–100 range, rendered as a horizontal progress bar with three colour bands (red / yellow / green).
  • Per-context thresholds (At-risk from, On-track from), with default values (40 / 70) when a context isn't yet configured.
  • Accessible indicator (role="progressbar" + aria-label).
  • JQL with standard numeric operators.

New Features — Workflow Extensions

• "Field Dependency" Validator:
  • New transition validator that blocks the transition only when a condition is met: a trigger field holds a specific value and, in that case, a required field is empty.
  • Multiple rules per validator, each with its own trigger → required pair and its own custom error message.
  • As triggers it supports the system fields Priority and Issue Type, plus custom fields of type Single-select List and Radio Buttons. The trigger list values are loaded automatically from Jira.
  • Complements the Fields Required validator: both can coexist on the same transition.

Improvements

• Cancel/Save buttons removed from the create view: removed the duplicated internal buttons in the create-view forms of the add-on's fields (Email, Phone, Traffic Light KPI, Currency and Percentage). These fields now integrate with Jira's native Create / Cancel dialog buttons, avoiding confusion and preserving consistency with the native UI.

Technical Notes

• Platform: Atlassian Forge, runtime nodejs24.x.
• UI technology: UI Kit 2 (@forge/react) for the custom fields; Custom UI (Vite build) for the Field Dependency Validator configuration UI.
• Distribution: Forge install link (outside the Marketplace) with automatic updates.
• Compatibility: any Jira Cloud site (Free, Standard, Premium, Enterprise), including Jira Service Management spaces.

Release 1.0.0 · Forge 2.0.0

First Forge version in production

From this release onward, the installed version appears in Apps → Manage apps as 2.0.0.

First Stable Release on Jira Cloud

Initial release of the Admin Essentials for Jira suite, built on Atlassian Forge. This first version ships the core workflow validation capabilities and the most-requested custom field types, with functional parity to the Data Center version of the add-on.

New Features — Custom Fields

• Email field (jira:customFieldType):

  • New Email Custom Field type available for Jira Cloud spaces and JSM spaces (both agent view and customer portal).
  • Format validation on the client (inline edit) and the server (via a Jira expression declared in the Forge manifest).
  • Enforces RFC 5321 limits: maximum 254 characters in total and 64 characters in the local part.
  • Automatic rendering as a clickable mailto: link (RFC 6068) on the work item view.
  • Support for inline editing from the work item view.
  • JQL search with exact-match operators (=, !=, in, is EMPTY, etc.).

• Traffic Light KPI field (jira:customFieldType):

  • New numeric field type rendered as a three-color indicator (🔴 red / 🟡 yellow / 🟢 green) based on per-context thresholds.
  • Per-context thresholds (Low threshold, High threshold) configured via Forge's contextConfig module, supporting different thresholds per space or work type.
  • "Lower value is better" mode to invert color semantics for KPIs where a lower value is desirable (resolution time, open issues, etc.).
  • Descriptive legend below the indicator and hover tooltip that communicate the active rule.
  • Native dark-mode support through UI Kit 2 design tokens (color.text, color.text.subtlest).
  • JQL search with standard numeric operators (=, <, <=, >, >=, is EMPTY, etc.).
  • Functional parity with version 1.2.0 of the Data Center Traffic Light field.

New Features — Workflow Extensions

• Fields Required validator (jira:workflowValidator):
  • New transition validator that blocks the transition when selected fields are empty.
  • Custom UI configuration panel with a dual list (available fields / selected fields) and a search box.
  • Support for a custom error message and an Ignore context option to enforce validation even on contexts that don't apply.
  • The validation rule is materialized as a Jira expression generated when the configuration is saved, which guarantees native execution by Jira and compatibility with transition-screen fields (including the Comment field).

Technical Notes

• Platform: Atlassian Forge, runtime nodejs24.x (arm64), 256 MB.
• UI technology: UI Kit 2 (@forge/react) for custom fields; Custom UI (Vite build) for the validator configuration UI (needed to generate the Jira expression on save).
• Distribution: Forge install link (outside the Marketplace) with automatic updates.
• Internationalization: UI strings served from translations/en-US.json via useTranslation() from @forge/react. Base language: English.
• Compatibility: any Jira Cloud site (Free, Standard, Premium, Enterprise), including Jira Service Management spaces.