Behaviours give you more control over fields in Jira. A field configuration customises how fields behave, based on the issue operation screen they appear on. However, a behaviour in ScriptRunner allows you to take that field customisation further, defining how fields behave for issues in a given project or issue context.
You can create behaviours to:
Make a field mandatory depending on other data entered on the issue screen.
Make a field read-only dependent on user role or group.
Conduct server-side validation of field data, before the issue screen is submitted.
Set a field value depending on other issue screen data.
For example, you give users the option to select a checkbox when they do not know their SEN (Support Entitlement Number). You can set up a behaviour to show additional fields when this checkbox is selected, to collect the information required to identify them.
Be sure to read through the Behaviour Limitations documentation before using a behaviour, or if you’re having problems getting your behaviour to work.
|New to behaviours? Check out our Behaviours Tutorial.|
Navigating to Behaviours
Click the Cog in the top ribbon to open the Administration menu and select Manage Apps.
Select Behaviours from the side menu under ScriptRunner. Here you can view and edit existing behaviours.
To add a new behaviour, enter a Name and optionally, a Description under Add Behaviour.
Have questions? Visit the Atlassian Community to connect, share, and learn with other Atlassian users and experts, including Adaptavist staff.
Want to learn more? Check out courses on Adaptavist Learn, an online platform to onboard and train new users for Atlassian solutions.