I'm testing to create a Dynamic Forms in a Ticket and I would like to add a Jira custom field I created into Forms in Jira Cloud
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:
Three constraints that often catch people:
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.
If you’re using Jira’s native Dynamic Forms, the first thing to check is whether the custom field is available on the relevant work item type screen and field configuration. In many Jira setups, a custom field won’t appear in forms if it isn’t associated with the project, work item type, or screen used by that ticket, but you cannot create it directly, only select from the avaliable options
Another approach you might consider is Smart Forms for Jira, developed by my team. In Smart Forms, you don’t necessarily add the Jira custom field itself as a form element. Instead, you create a form element that matches the type of data you want to collect — for example, dropdown, text field, checkbox, date, number, URL, etc. — and then map that form response to Jira field fields
For example:
Form field: “Business Unit”
Jira custom field: “Label”
Result: when the form is submitted, the selected value of selected form element is written into the Jira custom field or your choice.
So you dont need to create a custom field each time a new form entry should be gathered
This is useful when you want the form to stay user-friendly, but still keep the Jira work item structured for reporting, automation, routing, or dashboards.
If the custom field has predefined values, such as a select list, radio buttons, checkboxes, priority, components, versions, assignee, or reporter, Smart Forms can also populate form options from Jira issue fields. That helps keep the form options aligned with Jira.
Not every answer needs to be mapped to a separate Jira field, you can also map multiple form responses into the Description field for example and have a bundled form responses in the description to keep your Jira issue screen cleaner. Or even have some responses form only, without Jira mapping
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In the form, you can create a field and link it with your custom field, so, everytime it gets filled, its value will be stored in the field you created.
You can even give it a name, so you can use it in automations.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.