What are Behaviours in Jira?
Luckily the Script Runner for JIRA provides ‘Behaviours’. A behavior defines how fields behave for issues in a given project or issue context. Some examples of behaviors are: Making a field mandatory depending on other data entered on the issue screen (i.e during an issue creation or an issue transition)
How do I add a behavior in Jira?
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 Behaviours. Here you can view and edit existing behaviours.
- To add a new behaviour, enter a Name and optionally, a Description under Add Behaviour.
How are behaviours similar to field configurations in Jira?
Behaviours are similar to field configurations but enable you to work with additional options. As a reminder, a field configuration in Jira defines how fields in your instance act and can handle tasks such as setting hidden/visible fields or required/optional fields.
What do you need to know about Jira triggers?
This is where you can build compliance into your processes, deploy automation and amp up efficiency. Designed for software developers, triggers make your Jira workflow responsive to work that’s happening in linked development tools (Bitbucket, FishEye/Crucible, GitHub).
When do you use conditions in Jira workflow?
Conditions can be used to control who transitions an issue (only users who are members of certain groups, only users who have certain permissions, only the assignee, etc.). Conditions can also be used to ensure that an issue has passed through a required status, or that a fields contains a required value.
What do you need to know about transitions in Jira?
Statuses and transitions are the heart and bones of Jira workflows. However, you’ll get more out of your workflows if you dig into the details and use behaviors on your transitions. This is where you can build compliance into your processes, deploy automation and amp up efficiency.
