Understand the core concepts of VIP.LEAN Behaviours Builder. Learn what Behaviours, Conditions, and Actions are, and how they work together to automate Jira field modifications.
A Behaviour is a container that holds a set of Conditions and Actions operating within a shared context. Behaviours allow you to group logic and define a specific context for this group.

Each Behaviour includes:
Contained Artefacts:
The creation of a behaviour is always the first step in a logical workflow.
In addition to Behaviours, the Jira Admin can begin setting up the necessary conditions for Actions that will modify fields based on specific criteria. The Jira Admin also has the option to add conditions directly from the Action setup.
Conditions are not mandatory to create actions later. They are stored centrally and can be reused by any actions within behaviours.
A Condition includes:
The app identifies for which screens the condition is usable: Create, Transition, View. This is based on the technical background of the conditions. For example, check links can be done only after a work item has been already created (View / Transition).
The Action outlines the specific modification the Jira admin intends to implement on a chosen target field.
An Action includes:
• Name: A label to identify the Action.
• Target Field: Each Action specifically targets a selected Field. Multiple Actions can operate on different or the same fields. In case of conflicts, Atlassian provides a built-in warning, enabling the Admin to make adjustments.
• Screens: Each Action can function across a combination of the following screens: Create, View, and Transition.
• Event Type: An Action can trigger after a screen loads and/or with every screen change.
• Conditions: The Jira admin can establish either conditioned or non-conditioned Actions. Predefined Conditions can be combined using logical operators.
• Modification: This refers to the UI Modification that the Jira admin configures using specific fields tailored for each Field type.
The creation of behaviour actions is the last step in a logical workflow.
Venenatis sollicitudin posuere elit consequat et enim. Neque tortor amet dictum tempor. Leo facilisis aliquet viverra scelerisque eleifend viverra est. At massa erat vel amet enim laoreet dictum pellentesque. Urna cursus quam pulvinar tellus. Duis fermentum nibh volutpat morbi. Et ac sed ultricies ut nunc.
Et urna ac et maecenas fusce amet. Nibh nec commodo massa sed. Tincidunt porttitor in pharetra egestas sit neque ac lacus. Amet a nunc et cum. Odio at volutpat volutpat in leo eget ipsum diam elementum. Erat magna arcu orci.
Quis faucibus massa sit egestas. Sit fermentum est ac pulvinar et sagittis sed sit ut. Quis faucibus aenean nibh vestibulum enim mi sit. Sollicitudin ultrices ultrices in ipsum urna fringilla massa leo. Sapien ultricies vitae rhoncus molestie purus. Urna urna dolor euismod porttitor et. Magna adipiscing dictum et adipiscing.

Quis faucibus massa sit egestas. Sit fermentum est ac pulvinar et sagittis sed sit ut. Quis faucibus aenean nibh vestibulum enim mi sit. Sollicitudin ultrices ultrices in ipsum urna fringilla massa leo. Sapien ultricies vitae rhoncus molestie purus.
Cursus curabitur euismod vel fermentum sapien non dolor odio vel. Tortor lectus mauris in praesent a tincidunt nam. In aenean odio aliquet pretium viverra elit quis magna. Eget ut risus posuere velit purus nisi nec sollicitudin tellus enim.
“Sed id mi eget urna facilisis pharetra. Nunc viverra est at magna maximus consectetur. Sed nec maximus augue. Aliquam commodo sem eu.”
Cursus curabitur euismod vel fermentum sapien non dolor odio vel. Tortor lectus mauris in praesent a tincidunt nam. In aenean odio aliquet pretium viverra elit quis magna. Eget ut risus posuere velit purus nisi nec sollicitudin. Tellus enim interdum neque sit vestibulum lacus. Nam pulvinar a lectus justo aliquet.
Sed non quis tellus velit orci. Quam sed mauris elementum tempor viverra. Luctus semper risus ipsum id diam praesent. Pretium eget mauris ultrices curabitur sed sem amet. Erat nulla habitant in mattis massa mi adipiscing.
Sed non quis tellus velit orci. Quam sed mauris elementum tempor viverra. Luctus semper risus ipsum id diam praesent. Pretium eget mauris ultrices curabitur sed sem amet. Erat nulla habitant in mattis massa mi adipiscing ullamcorper condimentum. Erat quisque integer tincidunt ac amet.