Skip to main content
Version: 1.1.0

Changelog

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 issue 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 projects or issue 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 projects.

Release 1.0.0 · Forge 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 projects and JSM projects (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 issue view.
    • Support for inline editing from the issue 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 project or issue 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 projects.