What are Behaviours, Conditions and Actions?

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.

Content

    1. What Is a Behaviour?

    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.

    2. Behaviour Structure

    Each Behaviour includes:

    • Name: A label to identify the Behaviour.
    • Context Definition: A combination of Spaces and Work Types where this Behaviour is active.
    • Behaviours can have either draft, active, or paused status.

    Contained Artefacts:

    • Actions: Specify how the target field within the behaviour context should be modified.

    The creation of a behaviour is always the first step in a logical workflow.

    3. What Is a Condition?

    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:

    • Name: A label to identify the Condition.
    • Type of Condition: The app will offer continuously new condition types.
    • Condition Expression: The Jira admins enter the condition expression they need using pre-defined operators and entry fields, without any code or scripting.

    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).

    4. What Is an Action?

    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.

    ℹ️ Target Field Requirement: The target Field must be part of the screen you configured for the action, in the project and work type context of the behaviour parent.