Changelog

Release 1.5.0

Time tracking totalizers and updated official logo.

✨ New Features

• Time tracking totalizers:

  • The totalizer bar now supports three Jira system fields: Original Estimate, Time Spent, and Remaining Estimate.
  • The three fields appear grouped under the Time Tracking category in the selector in the View tab, separated from custom numeric fields.
  • Values are summed in seconds and expressed in hours with up to one decimal place (e.g. 50h, 40.5h). Null or missing values are treated as zero.
  • Time tracking fields and custom numeric fields can be combined in the same bar, up to the 5-field limit.
  • Configuration remains context-specific, just like all other totalizers.

• Official framed logo:

  • The add-on launches a redesigned official logo with a mobile-app-style frame, unifying its visual identity with the rest of the MB Group add-on suite.

📝 Technical Notes

• Time tracking totalizers are compatible with the custom numeric field totalizers introduced in version 1.4.0. No migration is required.
• Compatible with Jira Data Center 10.3.0 or higher.

Release 1.4.0

Configurable totalizers per context, compact issue view, and a cleaner browser console in the portal.

✨ New Features

• Configurable totalizers per context:

  • Administrators can enable a totalizer bar from the field configuration, selecting one or more numeric fields of the linked issues to sum.
  • The bar displays the sum of each selected field in an aggregated row that appears above or below the issue list, based on the configured position.
  • The configuration is independent per context: the same field can have different totalizers —or none at all— depending on the active context. All changes are recorded in the Audit Trail.

• Compact view with "Show all" option:

  • In fields configured in Multiple selection mode with more than 10 linked issues, the field displays the first 10 by default.
  • A "Show all (N)" link indicates the total number of issues and allows the user to expand the full list.
  • Once expanded, a "Show less" link appears to collapse the view again.

🛠️ Bug Fixes

• Cleaner JSM portal console: Debug messages that the add-on emitted in the browser console while using the field in the Jira Service Management portal have been removed. The console remains clean during normal use; diagnostic messages can be re-enabled via the issuepicker-portal-debug key in the browser's local storage.

📝 Technical Notes

• Totalizers extend the per-context configuration model introduced in version 1.2.0. No migration is required.
• The compact view applies to the field view on Jira issues; it does not affect the incoming references panel or the JSM portal.
• Compatible with Jira Data Center 10.3.0 or higher.

Release 1.3.3

🛠️ Bug Fixes

• JQL filters with Issue Picker field variables now work with multiple values: Fixed the behavior of dynamic JQL filters between Issue Picker fields when the source field has more than one ticket selected. Previously, a configuration such as key in ({{issue.customfield_XXXXX}}) returned 0 results if the referenced field had several tickets. The add-on now resolves each ticket in the source field to its issue key and generates the correct clause, regardless of how many values the field contains.

📝 Technical Notes

• No migration or field reconfiguration is required.
• Compatible with Jira Data Center 10.3.0 or higher.

Release 1.3.2

🛠️ Bug Fixes

• Incoming References panel visible for Multiple-selection fields: Fixed an issue where the Incoming References panel did not appear on an issue when the link originated from a field configured in Multiple selection mode. The panel now correctly displays all issues linking to the current issue, regardless of the selection mode of the source field.

• Correct Selection Type shown in the administration panel: Fixed the Selection Type column in the Main Administration Panel. Previously, it displayed Single for fields whose per-context configurations had different modes. It now accurately reflects the mode configured per context; if a field has contexts with different modes, the column shows Varies by context.

📝 Technical Notes

• The Incoming References panel works immediately after the update without reindexing. However, it is recommended to perform a reindex of Issue Picker fields after updating to optimize the performance of direct JQL searches on these fields.
• Compatible with Jira Data Center 10.3.0 or higher.

Release 1.3.1

🛠️ Bug Fixes

• Associate multiple tickets without a 255-character limit: Removed the restriction (~255 character limit) that prevented adding new tickets to a field configured in multi-select mode when the volume of associated issues exceeded a certain threshold. Users can now relate any number of tickets without data being truncated or saving being blocked.

📝 Technical Notes

• No migration action required. Existing fields retain their associations without changes.
• Compatible with Jira Data Center 10.3.0 or higher.

Release 1.3.0

✨ New Features

• Official Cloud migration path (JCMA): Jira Issue Picker DC is now integrated with the Jira Cloud Migration Assistant. When migrating your Data Center instance to Cloud, Issue Picker field values and their per-context configuration (JQL, selection mode, view attributes, incoming links panel title) are automatically packaged and delivered to the Dynamic Work Item Picker (Cloud) add-on, preserving all historical data without manual intervention. See the new Cloud Migration guide for process details.

Release 1.2.2

🐛 Bug Fixes

• Strikethrough on resolved tickets in the references panel: Fixed the rendering of the strikethrough over the issue key in the Incoming Links panel, so resolved tickets are now displayed with the expected strikethrough. The status badge alignment in the panel rows has also been improved.
• Incoming Links title with multiple contexts: Fixed the title resolution of the incoming links panel when the field has several contexts with different titles. The panel now honors the title configured for the issue's active context instead of always showing the default title.

Release 1.2.1

✨ New Features

• Status in References Panel: The status column has been incorporated into the references panel. This improvement provides immediate context on the situation of each linked ticket, facilitating the management and tracking of complex processes in Jira DC.

Release 1.2.0

✨ New Features

• Configuration by Context: Added the ability to configure 'Issue Picker' fields by context, allowing specific configurations for different projects or issue types and facilitating field reusability.

Release 1.1.0

✨ New Features

• Jira Service Management (JSM) Compatibility: The Jira Issue Picker field is now fully compatible with JSM portals. Users can search and select issues directly in the portal's request creation and viewing forms, with the same user experience as in Jira Software or Core issues.

Release 1.0.3

✨ Improvements

• Audit logging has been implemented for the "Title for incoming links" field, improving the traceability of configuration changes.

🐛 Bug Fixes

• Fixed a display issue that showed incorrect symbols in some Spanish words within the field configuration.
• Fixed a bug in the format of the dynamic variable value.

Release 1.0.2

✨ New Features

• View Incoming Links: A new panel has been added to the issue view that displays all issues linking to the current one through a "Jira Issue Picker" field, improving relationship visibility.
• Support for Dynamic Variables in JQL: It is now possible to use variables (e.g., {{issue.customfield_10500}}) in the field's JQL to filter results dynamically based on the issue's context.
• Audit Log Implementation: An audit log has been integrated to record all changes made to the configuration of "Jira Issue Picker" fields, enhancing security and control.

🐛 Bug Fixes

• = operator in JQL queries: Fixed a bug that prevented the use of the equality operator (=) in direct JQL searches on the field, restoring exact search functionality.

Release 1.0.1

✨ New Features

• JQL Search Support: It is now possible to use the Issue Picker field as a search criterion in Jira's JQL. This allows creating filters, reports, and dashboards based on the field's content. The search is performed by the issue's key and supports the !=, IN, IS EMPTY, and IS NOT EMPTY operators.

🐛 Bug Fixes

• Multi-select field size: The default visual size of the field when configured for multi-selection has been corrected, improving usability.