Frequently Asked Questions (FAQ)
Q: Where do I find the field's configuration page?
A: Unlike other add-ons that add their own administration page, the Dynamic Work Item Picker configuration is integrated with Jira. You can find it by navigating to Settings > Work Items > Custom fields, finding your field, and clicking on Contexts and default value > Edit custom field configuration.
You can find a more detailed guide here.
Q: Who can configure the field and who can use it?
A: From version 5.9.0 onward, field configuration (JQL, contexts, view, totals, selection type) requires Jira Administrator permission. Standard users with their usual Jira permissions can still edit the field value on work items (create, transition, portal) without being administrators. This distinction does not affect the picker experience for end users.
Q: Why can't I find a specific Work Item when searching?
A: This can be due to two main reasons:
- Jira Permissions: You can only search for and select Work Items that you have permission to see in Jira. Make sure you have access to the Space of the Work Item you are looking for.
- JQL Filter: The administrator may have configured a JQL filter on the field that restricts the results. For example, the field may be limited to showing only Work Items of a specific type or status.
Q: What is the difference between the Cloud and Data Center versions?
A: Both versions share the same core goal: linking Jira work items through a configurable custom field. The Cloud version is built on Atlassian Forge and distributed through the Atlassian Marketplace, while the Data Center version is installed manually as a .jar plugin. Current Cloud capabilities include single/multiple selection, per-context JQL filtering, view customization, Incoming Links panel, administration dashboard, audit trail, and per-context totals. The end-user experience is equivalent; the differences are concentrated in the installation, licensing, configuration, and update flows.
Q: Which version do I have installed?
A: For Cloud (Forge) add-ons, the version an administrator can verify is the one shown in Apps → Manage apps (for example, 5.4.0). That is the Forge version.
On this documentation site, the version selector may show:
- The Forge version (post-Forge), when the release is already published to production.
- The
(pre)suffix (for example,2.0.1 (pre)), for internal MB Group releases not yet visible in Manage apps.
See the mapping table in the changelog to relate each MB Group release to its Forge version.
Q: Why don't I see the comments button (💬) on the field rows?
A: The comments button is an optional feature that must be enabled by an administrator. If you do not see it, check with your administrator whether the Comments toggle is enabled in the View tab of the field configuration. Keep in mind that the button only appears in view mode (read-only); it is not shown while editing the field.
Q: Why is the 💬 icon highlighted in blue?
A: The icon is highlighted when there are comments published on that ticket after the last time you opened the modal for that same ticket. It is the unread comments indicator: it means there is new activity you have not reviewed yet. Opening the modal updates the state and the icon returns to its normal appearance.
Q: Why don't I see images inside comments?
A: Images embedded in Jira comments are displayed as the [media] placeholder in the modal. This is a limitation of the Atlassian Forge runtime environment (UI Kit). Text, tables, lists, and other ADF elements are displayed correctly.