Hi @Duong Nguyen Hong, @Juan Carlos Pin's direction is correct. To make it concrete and avoid the most common pitfalls, here are the exact steps and the gotchas around mapping a Jira custom field into a form.
The capability is called Linked Jira field on Atlassian's native forms (the same engine for Jira Software, Jira Service Management, and Jira Product Discovery). Steps:
- Open the form in the form builder (you need to be a project admin).
- Click the form field you want to map.
- In the right hand panel, locate Linked Jira field and pick your Jira custom field from the dropdown.
- Save the form. From that point on, whatever the user enters in the form field is written into the Jira custom field on the work item, so it is queryable with JQL and usable in Automation rules.
Three constraints that often catch people:
- The types must match. A text form field links to a text Jira field, a date to a date, a single select to a single select, etc. If the dropdown doesn't show your custom field, the most likely reason is a type mismatch.
- A given Jira field can only be linked once in the same form. If you have two form fields both trying to write into the same custom field, only one mapping is allowed.
- If you are using a JSM request type, the same Jira field cannot live on the request form (the legacy field configuration) AND on a form at the same time. Pick one. Putting it in both produces duplicate behaviour.
Official doc with screenshots: Link a form field to a Jira field.
If by "Dynamic Forms" you actually mean a Marketplace app rather than Atlassian's native Forms, the concept is similar (form field → Jira field mapping) but the UI lives inside that app. Worth confirming which one you are using.
Hope this helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.