JSM dynamic forms & field behavior

Make Jira Service Management request forms and Jira create / transition screens respond in real time to the user's input. Show, hide, set, require, rename, and reshape fields with scripts running entirely inside Atlassian Forge.

Why dynamic field behavior matters

Static forms ask every question to every user. Dynamic forms ask only the relevant questions. The difference is huge in two places: JSM request forms - where every extra field hurts customer experience - and Jira create / transition screens, where wrong-shaped data costs the team hours of cleanup downstream.

For years, "field behavior" was a flagship use case for legacy Connect-based scripting tools. With Atlassian Connect reaching full end of support on 31 January 2027, those form scripts have to move to a modern runtime. The Atlassian-preferred path is the Forge UI Modifications module, and JiBrok Studio exposes it as a scriptable trigger.

The result: the same kind of "if Category is Hardware, show the Asset field and require it" rules you used to write - but now they run on Forge, stay inside Atlassian's cloud, and benefit from tenant isolation and automatic updates.

Three common dynamic-form scenarios

1. JSM cascading request

On a "Hardware request" portal form, show the Asset type field only when the request type is "New equipment", and require an Approver when the estimated cost exceeds €500.

2. Pre-fill on create

On the Jira create screen, prefill the Reporter, Component, and Labels based on the user's team membership - and lock the labels as read-only.

3. Transition-time guidance

On the "Resolve" transition, require Resolution notes and hide internal-only fields. Rename the screen's label set to match the team's vocabulary.

How JiBrok Studio delivers it

A complete uim API

  • uim.setValue(field, value)
  • uim.setVisible(field, true/false)
  • uim.setRequired(field, true/false)
  • uim.setReadOnly(field, true/false)
  • uim.setName(field, name)
  • uim.setDescription(field, text)
  • uim.setOptionsVisibility(field, options, true/false)

Plus convenience aliases like uim.hideField() and uim.showField() for readability.

Scoped triggers

Each UIM trigger is scoped to specific projects, issue types, JSM service desks, and request types, and covers both the "Create" and "Transition" contexts. The UIM trigger is a singleton - one per script - so a second set of scopes means a second script.

Full reference: UI Modifications docs.

A small example

JSM portal: show Asset type and require Approver only when needed.

// UIM trigger scoped to the "Hardware request" request type.
// Current form state is read from uimData.fieldValues
const kind = uimData.fieldValues?.customfield_requestKind?.value;
const cost = parseFloat(uimData.fieldValues?.customfield_cost?.value || 0);

// Show asset type only for "New equipment"
uim.setVisible('customfield_assetType',
  kind === 'new-equipment');

// Require approver when cost exceeds €500
uim.setRequired('customfield_approver', cost > 500);

// Always hide an internal-only field on the portal
uim.hideField('customfield_internalNotes');

Save it, add a UIM trigger scoped to your JSM service desk and the "Hardware request" request type. The script runs on every form change - the experience updates instantly for the user.

Dynamic forms without external infrastructure

JiBrok Studio's UI modifications run on Atlassian Forge - the form logic stays inside Atlassian's cloud, with no vendor backend in the path.

JiBrok Studio for Jira Cloud JiBrok Studio for Jira Cloud
JiBrok Message Field for Jira Cloud Message Field for Jira Cloud
JiBrok time in status Time in status for Jira Cloud
JiBrok time in status Time in Status (Forge) for Jira Cloud
Calculated Fields (Forge) Calculated Fields (Forge) for Jira Cloud
JiBrok Calculated fields Calculated fields (JBCF) for Jira Cloud
JiBrok Timer Timer field | SLA for Jira Cloud
JiBrok Stopwatch Stopwatch for Jira Cloud
JiBrok Time between dates Time between dates for Jira Cloud
JiBrok Fields panel for Jira Service Management (JSM) Fields panel for Jira Service Management (JSM)
JiBrok Display Linked Issues Display Linked Issues
JiBrok Display Linked Issues Display Linked Issues
JiBrok message field Message field
JiBrok time in status Time in status | SLA | Timer | Stopwatch
JiBrok Switch to User + Delegating SU (Jira) Switch to User + Delegating SU (Jira)
Group Delegate & Creation Management (Jira)
JiBrok Calculated fields Calculated fields (JBCF)
JiBrok Timer Field Timer Field (Forge) for Jira Cloud
JiBrok Stopwatch Field Stopwatch Field (Forge) for Jira Cloud
JiBrok Time Between Dates Time Between Dates (Forge) for Jira Cloud
JiBrok Display Linked Issues Display Linked Issues (Forge) for Jira Cloud
JiBrok Customer Portal Fields Panel Customer Portal Fields Panel (Forge) for JSM
rss
rss
rss