Importing automation rules in an Atlassian Government environment

You can import automation rules into an Atlassian Government environment. This is useful for when you have to move your data from a Jira or Confluence Cloud site to an Atlassian Government environment.

However, some rules may contain components that aren’t included. As a result, these components won’t be available in an Atlassian Government environment, and your rule won’t be able to be imported.

To import a rule that contains unavailable components, you’ll need to remove any of the following components from your rule and try again. You can view the list of unavailable components in Jira and Confluence on this page.

Jira

Triggers

Name

1

Incoming webhook

2

Object

3

Vulnerability found

Conditions

Name

1

AQL condition

Actions

Name

1

Create branch in Bitbucket

2

Create branch in GitHub

3

Create branch in Gitlab

4

Create feature flag in LaunchDarkly

5

Create object

6

Create Slack channel for incident

7

Edit Assets field attributes

8

Edit Object

9

Link vulnerability to issue

10

Lookup in Bitbucket

11

Lookup objects

12

Publish SNS message via IAM

13

Restart Virtual Machine in Azure

14

Run a query in New Relic

15

Run AWS SSM document

16

Send message to Amazon SNS topic

17

Send Microsoft Teams message

18

Send Slack message

19

Send Twilio notification

20

Send web request

21

Sends a message to a Channel in Microsoft Teams

22

Start runbook in Azure

Branches

Name

1

Branch on AQL

Confluence

Triggers

Name

1

Incoming webhook

Conditions

Name

1

AI condition

Actions

Name

1

Generate AI action items

2

Send Microsoft Teams message

3

Send Slack message

4

Send Twilio notification

5

Send web request

6

Summarize with AI

How to import rules in Atlassian Automation

 

Still need help?

The Atlassian Community is here for you.