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:

1. 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.
2. 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.

Q: Why don't I see the progress bar in the field?

A: The progress bar is an optional feature that the administrator must enable per context. Check with your administrator whether the Progress bar toggle is enabled in the View tab of the field configuration. Note also that if the field is empty, the bar is not displayed even if the toggle is active.

Q: An issue is in "Done" status but it doesn't count as resolved in the progress bar. Why?

A: The progress bar calculates the percentage from the Resolution, not the status. An issue in Done without a Resolution does not count as resolved. For an issue to count as resolved, it must have a Resolution set in Jira (e.g. Fixed, Done, Won't Fix, etc.), regardless of its status colour.

Q: I enabled Issue Links synchronisation but links are not appearing. What might be happening?

A: Check the following: (1) The user modifying the field must have the Link Issues permission in Jira. Without it, the field updates but native links are not created or deleted. (2) Verify that you have selected a link type in the field configuration. (3) Synchronisation is unidirectional: adding a native link from Jira's panel does not add the work item to the DWIP field.

Q: I have multiple DWIP fields synchronising the same link type on the same issue. What happens if I remove a work item from one of them?

A: The native link is shared among all fields that synchronise the same link type towards that work item. The link is only deleted when no DWIP field on the issue still contains that work item with that link type. To avoid unexpected behaviour, it is recommended to configure a different link type for each field.

Q: Does the DWIP status order change Jira's workflow?

A: No. The status order only affects how work items are displayed inside the DWIP field view. It does not modify Jira's native workflow, the transition order, or any other field. If you do not configure an order list, the view behaves as before.

Q: When should I use the Automation action instead of editing the field by hand?

A: Use the native Jira Automation action when you want changes to the field to happen automatically in response to an event (for example, when an issue is created or moved to a given status), without manual intervention. Manually editing the field is still available for one-off changes made by a user while working on the issue. If the context has Issue Links synchronisation enabled, remember that the user or app running the rule needs the Link Issues permission for native links to be created or deleted correctly.

Q: Why did I used to have to wait between each removal when editing the field, and now I don't?

A: In previous versions, every click on the "x" saved and reloaded the field immediately, so removing several Work Items in quick succession could lose intermediate removals. Now changes stay pending until you confirm with ✓ or cancel with ✕: you can add or remove several Work Items in a row and everything is saved together on confirm. See Confirming or cancelling changes in the User Guide.

Q: Can I reuse the configuration of another Space or of another DWIP field?

A: Yes. In a context's configuration, use Copy configuration from… and choose as source another context of the same field or a context of another DWIP field on the same site. The form is filled in with the JQL, view, totals, status order, progress bar, Issue Links synchronisation, default value and note. Nothing is saved until you click Save changes, and the source context does not change.

Q: Does copying the configuration change the work items already saved on issues?

A: No. Copying only affects the field configuration of the target context. The work items already selected on each issue stay as they are.

Q: Does copying the configuration change the selection type or the context scope?

A: No. The target context keeps its scope (the Spaces and work item types defined in Jira) and its selection type (single or multiple). If the source uses a different selection type, the app warns you. The Ignore Space context option is not copied either: the target keeps its own.