Upgrading / Migrating
Upgrading Lite to Pro
Well done on making the excellent choice in upgrading from Lite to Pro. No longer are you restricted to 300 rule executions per month (Cloud) or can only use certain features (Server). It's time to go automation crazy! You can find out more about the differences between Lite and Pro from this handy guide.
All rules you've configured in Lite will still be there after the upgrade.
- From your Jira settings, navigate to "Find new apps" and launch the Atlassian marketplace
- Enter "Automation for Jira" into the search box and hit the enter key
- Select "Free Trial" for "Automation for Jira"
- Select "Accept and install"
- Automation for Jira automatically installs itself and confirms a successful installation
- You can check that all your rules from the Lite version are still there and operational by accessing Automation for Jira from the project and global settings.
If you encounter any difficulties during the installation, for example if "Licensed and Ready to go!" doesn't appear, go into your apps and if you see the Pro version there, uninstall it and try again. We are aware of some inconsistencies in the licensing road with Atlassian Marketplace.
Uninstall Lite once you have installed Pro. This keeps things nice and clean. You can uninstall it from "Manage Apps", and don't worry, you won't lose any of your rules.
Downgrading from Pro to Lite isn't as easy, but can be done by completely uninstalling the Pro version first, then re-installing Lite.
Extending your server evaluation period
Sometimes one month just isn't enough to evaluate a product and the good folks at the Atlassian Marketplace offer server customers a way to generate an extended evaluation license!
- Navigate to https://my.atlassian.com/ and login (you may have to ask your Atlassian Billing contact to do this for you)
- Find Automation for Jira in the list of licenses and expand it
- Select New Evaluation license
- Copy and paste the license key
- In Jira navigate to Global Admin > Manage add-ons > Automation for Jira and paste the license key!
Note: This is currently only available in server.
Import / Export
Automation for Jira provides a global import and export functionality for all and/or individual rules. This can be used for:
- Backing up rules
- Copying rules from one Jira instance to another
- Versioning rules in an external system
Import/Export is only available to global administrators. In the automation rules global admin section, hit the '...' menu top right to import or export all or individual rules.
If you uninstall and reinstall Automation for Jira (or upgrade / downgrade) you keep all your rules and data. You can also export your rules and then reimport them.
Please note that the JSON export has to be from the same version of Automation for Jira, or an import may fail.
Importing rules allows global administrators to select exactly which rules to import and with which project context. Imported rules have to be manually enabled after importing as all rules are imported as disabled. If a rule with the same name already exists, the imported rule's name is prefixed with
Copy of *existing rule name*.
Migrate from Server to Cloud
Congratulations and welcome to world of "The Cloud" - a place where Leprechauns sing and Unicorns fly.
Data-wise, the main difference between Server and Cloud is around user identifiers - with Server using usernames/keys and Cloud using "account id". There are 2 approaches in when migrating to Cloud:
- Recreate rules - this is the recommended approach and if you don't have many rules can be quicker.
- Manually map users
This is not the recommended way as it can be extremely hard to get right. We are tracking improvements for this here.
- You have the latest version of Automation for Jira on your Jira server instance (this ensures data compatibility between Cloud and Server)
- You have migrated your Jira data from Server to Cloud. This is to ensure that rules configured with Jira objects (for example a particular worfklow status) will exist with the same IDs in your Jira Cloud instance
- From Jira Server global automation admin (Global Admin > System > Automation rules), select the drop down in the top right followed by "Export rules"
- Open up your exported rules file in an editor and perform the following:
Look for where we reference users - Rule owner, user conditions, issue conditions, create/edit/transition issue actions. It should have a format like:
and replace with:
"id": "<user account id>"
To find the account id, navigate to the user in Cloud admin and use the last part of the url:
The user account id of this user would be:
JQL statements using user fields may also need to be updated with the account id (replacing the username/keys). Components that use JQL are: Scheduled triggers, Assign action, Branch components and Related issues condition.
- From Jira Cloud global automation admin, select the drop down in the top right followed by "Import rules" and follow the wizard
- Manually enable all the rules and fix any that have validation errors.
Audit log data is not migrated, this starts from scratch.