Pre-fill form options from work item field

Dynamic dropdowns, powered by your real Jira data

Pull predefined values straight from Jira work item fields — into your form elements. Options are populated dynamically, so the person filling out the form chooses from relevant, up-to-date data already stored in Jira.

How to set up

① Pick a supported element → add a Dropdown, Multi-choice, Checkboxes, or Radio buttons element.
② Point it at a Jira field → choose which work item field supplies the values (e.g. Priority, Components, Labels, Assets).
③ Options load automatically → the element fills with live values from that field, shown with the Jira-field icon.

④ Use the answer downstream → on submit, the selected value can update an existing work item or create a new one with the value pre-filled.

What you can pull in

Supported form elements

Supported Jira field types

Populate options from any of these work item fields:\

💡 Option count & order. If you select the project of the Jira field in the settings, all options load in their original Jira order. Without a project selected, you'll get up to 15 options.

Assets object fields

When the source is an Assets object field, the form loads objects from an Assets object schema so respondents pick real objects.

Selecting the field and selecting the schema are two separate choices:

• First please select The Assets custom field is where the selected object can be written back when creating or updating work items. A work item can carry more than one Assets field, each its own custom field.

  

• The object schema is the pool the respondent picks from. An Object schema dropdown appears when you select an Assets field. Pick the schema that holds the objects you want.

  

Narrow the list:

Open the Assets filter scope settings to control which objects appear:

• Select object type: show only objects of one type, instead of every type in the schema.

• Filter scope by another form element: make this element depend on an earlier answer. Pick the Source element, which is another Assets element in the form, and the Related through attribute, which is the reference that connects the two object types. The respondent then sees only the objects related to what they chose in the source element. Related through stays disabled until a source element is selected.

  

Good to know

Works with

🔁 Update existing work item fields

After submission, the selected value can automatically update the matching Jira field. Example: pick "High" in a Priority dropdown → the work item's Priority updates to High.

• Single-choice elements can update single- or multi-choice Jira fields, label-type fields, or same-type fields (text, date, number). A Priority-populated field can update Priority, Labels, or Summary. Number fields only update number fields.

• Multi-choice elements can update multi-choice or label-type fields. A Labels-populated field can set multiple labels on the work item.

➕ Create a new work item with pre-filled values

When a submission creates a new work item, form values populate the new work item's fields.

• Single-choice elements can set compatible fields on the new work item. A Priority-populated field can set Priority, Labels, or text fields like Summary/Description. Number fields only set number fields.

• Multi-choice elements can set multi-choice or label-type fields. A Labels-populated field can set multiple labels on the new work item.

Example Scenarios

Use Case 1: Task Prioritization Form

• Scenario: A team uses a form to set task priorities.

• Form Element: Dropdown populated with values from the Priority field in Jira.

• Outcome: When a user selects High Priority, the Jira work item Priority field updates accordingly.

Use Case 2: Feature Request Form

• Scenario: A product team collects feature requests from customers.

• Form Element: Multi-choice checkbox populated with Feature Categories from a custom Jira field.

• Outcome: Selected categories populate the Work Item Labels field in Jira.

Use Case 3: Incident Reporting Form

• Scenario: An IT team uses a form to log incidents.

• Form Element: Radio buttons populated with Incident Types from Jira.

• Outcome: Selected incident type maps directly to the Jira Work Item Type field.