Skip to main content
Version: 1.0.0

Changelog

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.