Fresh terminology for automation rules and components

An automation ‘rule’ is now a ‘flow', and a ‘component’ is now a 'step’. You may notice some inconsistencies in the documentation while we make this change. Read more about the updates in Automation

Import and export Jira automation flows

If you're an Atlassian Government customer, some steps can’t imported in your Jira automation flows.

How to import flows in Atlassian Government Cloud

In Jira Cloud, you have the option of importing and exporting your automation flows. This is useful for when you have to move your data from one Jira Cloud site to another, or if your team is migrating from Jira Server to Jira Cloud.

Before you begin

You must be a global administrator to import and export automation flows. Learn more about global permissions.

Export your automation flows to a JSON file

Jira automation provides a quick way to export all your automation data into one file.

  1. In Jira settings, select System, then Automation flows. You’ll be navigated to the global Automation screen.

  2. In the top right corner, select More actions (…), then Export flows. This will download a JSON file containing all global and project-scoped automation flows.

Import your automation flows to a Jira Cloud site

Things to be aware of when importing automation flows

  • Server to Cloud: After migrating flows from Automation for Jira Server to Jira Cloud, you may have to reconfigure your flows. In particular, there’s a strong chance that data specific to your Jira instance such as Statuses, Issue types, or Fields and custom fields won’t map correctly and those flows will need to be reconfigured. Note than importing and exporting automation flows work only for one-to-one migrations, that is, from a single Jira Server or Data Center to one Jira Cloud site. This method is not supported incase of federation (one to many) or consolidation (many to one) of multiple instances into a single or multiple Jira Cloud site(s).

  • Cloud to Cloud: You may also need to reconfigure your flows when migrating from one Jira Cloud site to another, but this is more likely to be successful.

  • File limit: Your JSON file must be 5MB or smaller. If your file is too big, you can export your flow in multiple segments.

 

Once you have your JSON file, you can then import that automation data to any Jira site.

  1. In Jira settings, select System, then Automation flows. You’ll be navigated to the global Automation screen.

  2. In the top right corner, select More actions (…), then Import flows.

  3. Select Upload JSON or drag and drop your JSON file to the area inside the dotted line.

  4. Select the flows you want to import and the scope of projects for each flow.

  5. Optional: Select Import flow owners to import the flow owners from your file. If this isn’t selected, the person who imported the flows will be listed as the flow owner.

    • If importing from Server/Data Center: You’ll need to manually change the account IDs for your flow owners, because these are different in Cloud.

      If importing from Cloud: No changes need to be made to the JSON file, but you’ll need to ensure those users are in your Jira Cloud site.

  6. Select Let's do this to finish the import.

All imported flows will initially be disabled and you’ll have to enable them to use them. If a flow with the same name already exists, the imported flow’s name will become Copy of [flowname].

Still need help?

The Atlassian Community is here for you.