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.
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.
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.
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.
On the "Resolve" transition, require Resolution notes and hide internal-only fields. Rename the screen's label set to match the team's vocabulary.
uim APIuim.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.
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.
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.
JiBrok Studio's UI modifications run on Atlassian Forge - the form logic stays inside Atlassian's cloud, with no vendor backend in the path.