Configuring automation rules

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

You can create automation rules that automatically perform actions (e.g. notify users) based on specific events (e.g. object updated) for all objects, or only a group of objects in a schema.

Before you begin

Make sure you have the right permissions:

  • To configure automation rules, you need to have at least the Insight Manager role for the schema.
  • Tu run and execute automation rules, the user (either the logged-in user or the user that you select for running scheduled events) needs to have at least the Insight Users role for the schema. If this user has a different role for the object types affected by the rule (object type's permissions take precedence over schema's permissions), then also grant them the Insight Users role for these object types. This is only needed if a rule affects such object types, otherwise permissions are inherited from the schema.

For more info about permissions, see Configuring roles and permissions.

Create a rule

  1. Open your schema, and select Object schema > Configure.
  2. Switch to the Automation tab.
  3. Create a rule.
  4. Enter the rule's name and description.
  5. Click each of the boxes (WHEN, IF, THEN). A panel will appear on the right allowing you to add an event, condition, and action. You can read more about them below.

Any changes to your rule will only be saved after you click Save. If you've deleted something by mistake, you can click Cancel to revert these changes.

Configure your rule

Configure your role by specifying events (when), conditions (if), and actions (then).

1. Add events (WHEN)

  1. Select the WHEN box.
  2. On the right, click Add events.
  3. Choose the desired event and click Add.
tip/resting Created with Sketch.

Good to know

  • You can add up to 5 events for a single rule.
  • Instead of creating two or more rules with the same actions (for example, Email Notification), add two or more events to the same rule. It will be easier to maintain later.

Event types

Event typeDescription
User eventsMost events, except the Scheduled event are triggered when a logged-in user performs the action on an object (Object updated, Attachment added, etc.) These events don't require any additional configuration.
Scheduled events

Scheduled events aren't triggered by an action performed by a user. They run according to the specified cron expression (e.g. once a day, once an hour) and conditions. 

Required parameters for scheduled events...

Here are the required parameters for scheduled events:

  1. Condition: This is an IQL (Insight Query Language) expression. When the scheduled rule is activated, all objects that match the condition will trigger individual actions.
  2. Cron expression: This determines when and how often the provided condition will try to match insight objects. By default, the expression is set to " 0 0 12 1/1 * ? *", that is: once a day at noon. Learn more about cron expressions
  3. Triggered rule will run as: For schedule events, you need to choose a specific user here, because they can't be triggered by a logged-in user. You can choose the user on the top-right of the page.

2. Add conditions (IF)

You'd usually configure a condition when you don't want the configured action to apply to all objects in your schema, but rather a specific set of objects. 

  1. Select the IF box.
  2. On the right, click Add condition.
  3. Enter an IQL statement and click Add.
tip/resting Created with Sketch.

Good to know

  • A condition always comes in pair with a THEN box. When you add another condition, you'll be able to edit actions for it.
  • You can configure up to 3 IF/THEN pairs.


  • A rule has an event "Object Updated".
  • A rule has a condition "Name = Windows server".
  • A rule has an action "Notification Email".

This rule will only send a notification email if the object that was changed by a user has the exact name "Windows server". 

3. Add actions (THEN)

  1. Select the THEN box.
  2. On the right, click Add action.
  3. Choose your action and fill in the details. Every action requires different details, for example details needed for Create a Jira issue will differ from those needed to Execute a Groovy script.
  4. Click Add.
tip/resting Created with Sketch.

Good to know

  • You can have up to 5 actions for every THEN box.

Available actions

Here's a list of actions that you can choose:

Attribute value

This actions allows the rule to change the value of an object's attribute.

Set an attribute value of the Insight object affected by the event. Multi values are separated by comma (,)

FieldExample single valueExample multi value
Attribute nameStatusServer
ValueStoppedServer 1,Server2
Create Jira issue

This action allows the rule to create a Jira issue. Good to know:

  • (warning) The issue type selected must be available for the chosen project, otherwise a Jira issue can't be created.
  • (info) If the custom field is populated, the chosen project must be configured to handle this object type, otherwise this field won't have any effect.

Fields that support placeholdersExample syntaxExample result
SummaryServer ${label} stopped! Server ${} stopped!
DescriptionServer details - name: ${label}, key: ${Key}, id: ${objectId} Server details - name:, key: WS-5969, id: 17400 
Email notification

This action allows the rule to send email notifications related to the event that was triggered.

Example: For the Object updated event, an email will be sent showing the changes related to this object.

Fields that support placeholdersExample syntaxExample result
SubjectServer: ${label} is stopped.Server: is stopped.
MessageServer: ${label} (${Key}) has status: ${Status}.Server: (WS-5969) has status: Stopped.
Execute Groovy script

This action allows a triggered rule to execute a Groovy script.

  • (warning) Make sure the Groovy script has adequate permissions so it can be executed.

Data available to the Groovy script by our rule engine

ParameterDescriptionJAVA class

The Object that was directly involved in a user action (like updating an Insight Object) or matched by a scheduled rule through IQL, with an "Execute Groovy Script" as Action

Object that was directly involved in a user action (e.g. updating an object) or matched by a scheduled rule through IQL, with an "Execute Groovy Script" action.

User who triggered the rule or a specific user chosen to "run the rule.


Instance of the Apache Log interface, for convenient logging in a script.


List of object attributes that are affected in an object update event that includes affected attribute in an object, as well as added or removed values for it.

Http request

This action allows a triggered rule to make a HTTP request. It supports the standard HTTP methods: GET / POST / PUT / DELETE.

Fields that support placeholdersExample syntaxExample result
Post Data (POST / PUT){ "name":"${label}","key":"${Key}","id":"${objectId}" }{,key:WS-76100,id:76100 }

4. Add more conditions and actions

A rule can only consist of one event (WHEN), but it can have up to three pairs of conditions and actions (IF/THEN). This allows you to add more conditions and actions if the first ones aren't matched.

  1. Click the ELSE IF / THEN box.
  2. Add actions, and conditions if needed.
  3. Click Save.

More automation

Automation rules are related to a specific object scheme, but there's way more automation that you can add. Your Jira admin can add conditions and validators, as well as post-functions, to Jira workflows that will make issues affect objects while they're being transitioned through workflows. For more info, see Adding Insight functions to Jira workflows.

Last modified on Sep 8, 2021

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.