ContactBook a demo

Jira screens that adapt to the work.

Behaviours Builder shows, hides, requires, locks, fills and filters fields based on what the person is doing. No scripts. Live the moment you save.

Start free trial Book a setup session

Jira Cloud and Jira Service Management · 30-day evaluation · we set it up with you, free

Create work item Behaviours active

New item in IT Service Desk

Incident
What happened?
Select…
Select…
Medium
Derived from impact × urgency
Search assets…
Select…
Low / Medium / High
MK · Maria Klein
Pick a slot

Cycles through Incident, Problem and Change.

Five things a screen does when it knows the context.

Every one of them is a rule you click together. Scroll to see what each does to the same form.

Edit · HR-2041 Onboarding request
Engineering
MacBook Pro 16"ThinkPad P1MacBook AirThinkPad X1Surface Pro
dd.mm.yyyy
JB · Jonas Berg
Taken from the Department's lead
Choose sites…
Which repositories?
e.g. 4410
Start date must be at least 10 working days out

Show only what matters

A request for Engineering reveals repository access. For Sales it stays out of the way. The form gets shorter, the data gets cleaner.

Require it when it counts

Cost centre becomes mandatory once the laptop is a high-spec model. Required means required on the screen, not in a comment three days later.

Fill it from what you already know

The manager is derived from the department, then locked. Text, numbers and user pickers can all be set from other fields.

Filter the choices

Windows-only department? The Mac options disappear. People choose from a short, correct list instead of a long, generic one.

Validate before it's saved

A start date less than ten working days away is flagged where the person is looking, with a message you wrote in plain language.

Click through it yourself.

Three minutes in the real builder: a condition, a modification, and what the screen does afterwards. No install needed.

Load the interactive demo The demo is served by Supademo. Loading it transfers your IP address to Supademo; see our data protection notice.

Built for the admin who owns fifty projects, not one.

The hard part isn't one rule. It's hundreds of them, consistent, without a script repository.

One behaviour. Every space that needs it.

Apply the same rule to twenty spaces and six work types at once. Change it in one place; every screen picks it up.

Live on save.

No deploy, no cache, no waiting. Save the behaviour and open the screen.

Conditions you write once.

Groups, permissions, field values, user input, context. Combine with AND, OR and brackets. Reference from any behaviour.

Only valid options are offered.

Checked against Atlassian while you configure. What isn't eligible stays visible, with the reason.

You can see it working.

How often each behaviour fired, which actions it applied, where something needs attention.

Where it sits next to the alternatives.

Three honest ways to get dynamic screens in Jira Cloud today, and the trade-off each one makes.

Behaviours BuilderVIP.LEAN ScriptRunner BehavioursAdaptavist Dynamic Forms for JiraDeviniti Jira FormsAtlassian, built-in
Way of working Visual builder, click-together conditions Scripts (TypeScript/JavaScript) per behaviour Rule configuration per screen scheme and work type Form designer, attached to a request or work item
Scope of one rule Many spaces, work types and screens at once Per context mapping (project × work type × view) Per screen scheme, import/export to reuse Per form, and only inside the form
Acts on native Jira fields Create, edit, transition and JSM portal screens Yes Yes Form questions map to fields; the issue screen itself stays static
Derive values from other fields Text, numbers, user pickers, no code Anything you can script Limited to configured actions Not available
Tells you what won't work before you publish Continuous eligibility check with reasons You find out at runtime Supported-field list in docs Form-level only
Who maintains it Any Jira admin Someone who owns code Jira admin Project admin
Best when You want dynamic screens everywhere, kept consistent by one team You already run ScriptRunner and need logic no builder offers You need dynamic fields in a handful of spaces You only need better intake forms in JSM

Compiled from the vendors' public documentation as of September 2026. Products change; if we got something wrong about yours, tell us and we'll fix it. ScriptRunner and Dynamic Forms are trademarks of their respective owners.

Migrating from Data Center? Leave Groovy behind, not the behaviours.

Jira Cloud has no Groovy runtime. Instead of paying a developer to rewrite years of ScriptRunner behaviours as TypeScript, rebuild them as configuration a Jira admin owns.

  1. Read each script for its intentEvery behaviour answers three questions: where it applies, when it fires, what it changes on the field. The scripting is just how Data Center made you say it.
  2. Rebuild it as configurationScope once across spaces and work types, pick a reusable condition, choose the modification. Eligibility is checked against Atlassian before you can save.
  3. Sort the rest honestlyScripts can still do things no builder offers. We help you split your Data Center behaviours into “configure” and “still needs code” before the cut-over.

Bring your Groovy scripts to a working session; we map them together. Plan the behaviour migration

Jira Data Center · ScriptRunner Behaviour

GROOVY
1// PROC · Purchase request
2def p = getFieldById("priority")
3if (p.value?.name == "Highest") {
4 getFieldByName("Cost centre")
5 .setRequired(true)
6 getFieldByName("Approver")
7 .setHidden(false)
8} else {
9 getFieldByName("Approver")
10 .setHidden(true)
11}

Jira Cloud · Behaviours Builder

BEHAVIOUR
PROC · Purchase requestCreate · Edit · Transition
CONDITION
Priority is HighestREUSABLE
ACTION
Cost centreSet required
ACTION
ApproverShow
ACTION
ApproverHideNOT Priority is Highest
0 lines of code · built by a Jira adminELIGIBLE
setRequired(true)Set required
setHidden(true)Hide field
setReadOnly(true)Read-only
setFormValue(x)Set or derive value
setFieldOptions(...)Show or hide options
setLabel / setDescriptionLabel, description

Try it on a real screen this week.

Install from the Marketplace, then book a free working session: we'll build your first three behaviours with you. Solution Partners get stackable discounts of up to 30%.

Start free trial Book a setup session

Questions first? Read the docs or open a support ticket.