Skip to main content
Version: 1.3.0

Changelog

Release 1.3.0

This release focuses on discoverability and correct use of JQL for the Traffic Light KPI field. The threshold editor now displays ready-to-copy JQL queries, generated live from the real field name and the active context's thresholds. The plugin README is also expanded with a dedicated section on filtering by Traffic Light zone.

New Features

  • Traffic Light: JQL examples per context in the threshold editor:
    • The Edit Traffic Light KPI Thresholds form now includes a help block that shows, for each zone (red, yellow and green), the corresponding JQL query generated from the real field name and the threshold values entered in the form.
    • Queries update live as you modify Red max / Yellow max values or toggle the Lower is better option.
    • Copy button next to each query: one click copies the JQL expression to the clipboard, ready to paste into the issue search or a saved filter.
    • The help block includes a note explaining that JQL operates on the stored numeric value, not on the rendered color, and that the ranges are specific to the active configuration context.
    • Visual compatibility with Jira's dark theme via Atlassian Design System color tokens.
    • All texts in the new block are internationalized (i18n) in English and Spanish.

📝 Technical Notes

  • No changes to OSGi modules or field types: the update consists of UI templates, i18n strings and the repository README.
  • The add-on update is performed through UPM in the usual way; no data migration or reconfiguration of existing thresholds is required.
  • Compatible with Jira Data Center 10.3.18 or later.

Release 1.2.0

This release expands the suite with two new workflow extensions —a required-fields validator and a project-roles condition— and enriches the Traffic Light KPI custom field with a thresholds legend and tooltip, a new "lower is better" mode, and a contrast fix for Jira's dark theme.

New Features

  • Traffic Light: thresholds legend and tooltip on the issue view:

    • The issue detail view shows a descriptive legend with the configured threshold ranges, right below the indicator.
    • Hovering over the indicator displays a tooltip with the exact range the current issue value belongs to.
    • The legend and tooltip honor the user's language and Jira's active theme (light / dark).
    • Improves value comprehension without having to open the field configuration.
  • Traffic Light: "lower is better" mode (invert colors):

    • New Lower is better option in the Traffic Light field's threshold configuration, which inverts color assignment without changing the order of the thresholds.
    • Designed for KPIs where a lower value indicates better performance: resolution time, number of incidents, open defects, etc.
    • Configurable at the field context level, just like the existing thresholds (can be enabled in some contexts and not in others).
    • The legend and tooltip automatically reflect the active mode.
  • Required Fields on Transition validator:

    • New workflow validator that blocks the execution of a transition when certain issue fields are empty.
    • Configurable per transition: the administrator selects the required fields from a multi-select.
    • Supports a custom error message that is shown to the user when the transition is blocked.
    • When blocked, the message clearly indicates which fields are missing.
    • Compatible with both custom and standard Jira fields.
  • Project Roles on Transition condition:

    • New workflow condition that restricts the execution of a transition to users belonging to one or more selected project roles.
    • Configurable per transition: the administrator picks the allowed roles from a multi-select.
    • The evaluation is always relative to the issue's project, which makes it possible to reuse the same workflow across several projects without duplicating it.
    • Users without the required role do not see the transition among the issue's available actions.

🛠️ Fixes

  • Traffic Light numeric contrast in dark mode: fixed the contrast of the numeric text on the Traffic Light indicator when Jira uses the dark theme. The numeric value is now readable in both light and dark modes, preserving accessibility on any theme.

📝 Technical Notes

  • The "lower is better" mode is configured at the field context level, next to the existing thresholds. If the same field is reused across projects with different semantics, just enable it in the contexts that need it.
  • The new validator and condition are registered into Jira Data Center's standard workflow validator/condition catalog and can be combined with native rules (all of them are evaluated as AND).
  • All administrative and UI texts of the new features are internationalized (i18n) with English and Spanish support included.
  • Compatible with Jira Data Center 10.3.18 or later.

Release 1.1.0

This release extends the suite with a new Traffic Light KPI custom field and incorporates the add-on's official visual assets: the main logo and preview images for the available fields.

New Features

  • Traffic Light KPI Custom Field:
    • New numeric field type that renders a color indicator (🔴 red / 🟡 yellow / 🟢 green) on the issue detail view and in listings.
    • Configurable thresholds per context (Red max / Yellow max), allowing different rules per project or issue type from the field configuration page.
    • Color resolution by active context: the indicator is calculated from the thresholds of the context the issue belongs to.
    • Accessible rendering (aria-label tags per state) and compact view for columns and boards.
    • Integrated searcher (Number Range Searcher) for filtering and searching by numeric value via JQL (=, <, <=, >, >=).
    • The entire administration interface and validation messages are internationalized (i18n), with Spanish and English support included.
    • Compatible with Jira Data Center.

🎨 Design and Visual Assets

  • Official Admin Essentials add-on logo: the plugin's main logo (512×512 px PNG) is included, visually consistent with the suite's field icons.
  • Email field preview image: available on Jira's custom field creation screen, visually representing an email field (envelope and sample address).
  • Traffic Light field preview image: available on Jira's custom field creation screen, representing the three-bulb indicator (green / yellow / red).

📝 Technical Notes

  • Traffic Light threshold configuration is always tied to the active FieldConfigContext, allowing independent thresholds per project or issue type without duplicating the field.
  • While a context has no thresholds defined, field values render in gray (no state) to avoid communicating a color that could lead to misinterpretation.
  • This version's threshold model assumes "higher values are better". If your KPI works the other way around, model the thresholds by inverting the meaning of the range.

Release 1.0.0

🚀 First Stable Release

This is the first stable release of the add-on. Starting with this release, the plugin officially adopts the name Admin Essentials, reflecting its nature as a multi-module suite of utilities for Jira administrators.

New Features

  • Email Custom Field:
    • New Email custom field type available for Jira Data Center projects.
    • Allows recording one email address per issue, rendered as a mailto: link on the issue view.
    • Server-side format validation following the HTML5 specification (the same applied by browsers to <input type="email">), ensuring consistent data from any source (Jira screens, REST API, importers, and external integrations).
    • Applies RFC 5321 limits: maximum 254 characters total and 64 characters in the local part.
    • Integrated search support with the Jira engine: the field is searchable from basic search and JQL.

🛡️ Quality and Coverage

  • Unit test suite for the Email field, including edge cases (maximum lengths, special characters, and invalid inputs).
  • CI quality gates configured to enforce minimum coverage on each merge.

📝 Technical Notes

  • The plugin has been officially renamed to Admin Essentials as the user-facing name, laying the foundation for future modules.
  • Compatible with Jira Data Center 10.3.18 or later.