Gain control over your Jira fields with ScriptRunner
Create dynamic field rules to hide, show or customise Jira fields based on user actions, field selections, issue types, user roles and more.
Customise how fields behave in Jira Cloud across the issue lifecycle and gain complete control over your instance with ScriptRunner's Behaviours.
More focused, less cluttered Jira environments
Align Jira with your business processes
Automate field behaviours and enforce specific processes within Jira. Reduce manual work and unnecessary supervision by creating automated rules to eliminate errors and enhance productivity.
Enhance the user experience for your teams
Clarify and simplify your team's requirements by hiding irrelevant fields and displaying only what's needed. Reducing clutter and making issue creation and editing easier to navigate, improving user experience
Improve data quality and streamline issue management
Control field behaviours and add custom templates that guide your teams to enter information consistently and efficiently, improving the overall quality of your Jira issues and making content more reliable
ScriptRunner's Behaviours in action
When using Behaviours, you can unlock the type of responsive, logic-driven customisation that is not available natively in Jira.
This Behaviours app is available exclusively for ScriptRunner for Jira Cloud users.
Please update your cookie preferences below to view this content.
Ready to try ScriptRunner?
Start your 30-day free trial of ScriptRunner for Jira Cloud to get started today.
Most popular use cases
Set field value based on another supported field
Automatically assign a ticket to a specific person if the priority level is set to ‘High’.
Show or hide field based on another field
Show / hide field based on the selection of another field
Show the ‘Line Manager’ field when ‘HR' is selected in the Department field. If 'Finance' is selected, Line Manager is hidden, and 'Ticket Category’ is shown instead. Both fields are hidden if the 'Product' department is chosen.
Pre-fill a template
Pre-fill a template on a field based on the project and issue type
When a user wants to create a new Story under the ‘Engineering’ project, the Summary and Description fields are filled with helpful text that the user can then edit.
Make field mandatory
Make field mandatory based on the selection of another field
Make the ‘Ticket Reviewer’ field mandatory if the priority of an issue is set to ‘High’.
Change field name and add helper text
Change field name and add helper text based on the selection of another field
If the ‘Department field' is changed to ‘Product’, the 'Ticket Reviewer’ field automatically changes its name to 'Senior Dev Reviewer’, and helper text is added with more instructions.
Make field editable only by a specific user group
Make a read-only field editable by a specific user group based on the selection of another field
When Product is selected in the ‘Department’ field, make the ‘Senior Dev Reviewer’ field read-only for everyone except for the people in a specific user group.
Set field value based on another supported field
Automatically assign a ticket to a specific person if the priority level is set to ‘High’.
Show / hide field based on the selection of another field
Show the ‘Line Manager’ field when ‘HR' is selected in the Department field. If 'Finance' is selected, Line Manager is hidden, and 'Ticket Category’ is shown instead. Both fields are hidden if the 'Product' department is chosen.
Pre-fill a template on a field based on the project and issue type
When a user wants to create a new Story under the ‘Engineering’ project, the Summary and Description fields are filled with helpful text that the user can then edit.
Make field mandatory based on the selection of another field
Make the ‘Ticket Reviewer’ field mandatory if the priority of an issue is set to ‘High’.
Change field name and add helper text based on the selection of another field
If the ‘Department field' is changed to ‘Product’, the 'Ticket Reviewer’ field automatically changes its name to 'Senior Dev Reviewer’, and helper text is added with more instructions.
Make a read-only field editable by a specific user group based on the selection of another field
When Product is selected in the ‘Department’ field, make the ‘Senior Dev Reviewer’ field read-only for everyone except for the people in a specific user group.
It's very exciting to have this functionality available for Jira Cloud.
Joe Clark
Behaviours, ScriptRunner for Jira Cloud
Great app! A lot of functionality that is missing in Jira can be done through ScriptRunner. Also the customer service is spot on! I had a problem with a custom script and they helped until it was fixed. I'm very happy with this app and the customer service!
Thijs Rijnders
ScriptRunner for Jira Cloud
One of the best apps for Jira.
Hossein Ebrahimi
ScriptRunner for Jira Cloud
Supported across the entire issue lifecycle
Behaviours is supported on Create View, Issue View, and on Transition View.
Check out our Documentation for an up to date list of every supported field currently available.
Prioritising your data’s safety and privacy
As Atlassian Premium partners and leading technology providers, we take our responsibility seriously when it comes to data security, privacy and stability.
We're ISO 20071 accredited across the entire ScriptRunner suite, denoting excellence in data security and we've been issued a SOC 2 Type 2 audit report.
FAQs
Do I have to pay extra for Behaviours?
Behaviours is a feature of ScriptRunner for Jira Cloud and there is no additional charge for the Behaviours app. If you are already a ScriptRunner for Jira Cloud user, you can install and use Behaviours for no additional charge.
You can find out more about ScriptRunner for Jira here.
Is Behaviours supported on JSM Cloud?
Behaviours is not yet compatible with Jira Service Management (JSM) as JSM is not yet supported by Atlassian’s API.
The ScriptRunner team is aware that this is very important to customers and is working closely with Atlassian to bring Behaviours to JSM Cloud. We encourage anyone who’s interested to vote on FRGE-774 and provide details about their use cases in the ticket comments.
Atlassian expects to have a timeline for Behaviours/JSM compatibility later this year.
In the meantime, you can refer to the Behaviours documentation for information on currently supported features and watch the ScriptRunner for Jira Cloud Product Updates Hub for the latest information on what has been released and what is coming next.
Is ... [field, method, location, platform] supported in Behaviours?
All currently supported fields, methods, views / locations, actions and platforms can be found in the Behaviours documentation. These capabilities are available in Behaviours because they are supported in Atlassian’s UI Modifications API - that is, the API that Behaviours is built on.
If a specific capability (field type, method, location, platform etc.) is not supported in Behaviours, it's most likely because:
- it is not yet supported by Atlassian through their API.
- support for it has recently been added in the UI Modifications API, which means that it will soon become available in Behaviours on Jira Cloud as well.
If you have a suggestion for a new functionality that you would like to be added to Behaviours, please check and post on the ScriptRunner for Jira Cloud suggestion board.All currently supported fields, methods, views / locations, actions and platforms can be found in the Behaviours documentation. These capabilities are available in Behaviours because they are supported in Atlassian’s UI Modifications API - that is, the API that Behaviours is built on.
If a specific capability (field type, method, location, platform etc.) is not supported in Behaviours, it's most likely because:
- it is not yet supported by Atlassian through their API.
- support for it has recently been added in the UI Modifications API, which means that it will soon become available in Behaviours on Jira Cloud as well.
If you have a suggestion for a new functionality that you would like to be added to Behaviours, please check and post on the ScriptRunner for Jira Cloud suggestion board.
Why do I need to install another app to use Behaviours?
Behaviours is available as a companion app from the Atlassian marketplace. This is not a standalone app and can only be used when the main ScriptRunner for Jira Cloud app is installed.
A separate app for Behaviours is needed because ScriptRunner is built on Atlassian’s Connect platform, while Behaviours was only possible to build on the newer Forge development platform.
Can Behaviours be used without ScriptRunner for Jira?
No, Behaviours is not a standalone app. Behaviours will work only when the ScriptRunner for Jira Cloud app is also installed.
For new ScriptRunner and Behaviours users, there is no specific order of installation so you can install Behaviours first if you prefer. You will then be notified to install ScriptRunner to activate Behaviours.
What scripting language does Behaviours use?
The language used when writing the logic for Behaviours scripts is Javascript.
The language used in ScriptRunner for Jira Cloud is Groovy.
Where can I see the Behaviours status page?
Behaviours doesn't have a separate status page. You can see failure reporting for all Cloud apps on the ScriptRunner status page.
What can ScriptRunner do for you?
Book a 30-minute video call with one of our Customer Success Advocates to find out how ScriptRunner for Jira Cloud can help you accelerate your Jira automation and customisation journey.
Wanting to explore everything ScriptRunner for Jira Cloud has to offer?
