If you are currently using the old Atlassian Labs provided add-on v.2.0.3 you will see these add-ons installed in your JIRA instance:

Image Removed

If you upgrade to the new Lite version provided by Code Barrel (see the first 'Upgrade Scenario' above), you will have these add-ons installed:

Image Removed

The old "Automation Module" and "JIRA Automation SPI" add-ons can safely be uninstalled at some point in future. This will reduce memory footprint and startup times of your JIRA instance.

If you upgrade to the Pro version at some stage in future from our Lite version, then you should see the following add-ons listed:

...

• Who this guide is for
  • Server only
  • Mostly for users upgrading from the old Atlassian labs to Automation for JIRA
• Upgrade Scenarios
  • Labs → Lite
  • Labs → Pro
  • Lite → Pro
  • Third party extensions like Midori's PDF & Excel, nFeeds...
• Add-ons provided by the different versions
  • Show screenshot of old Labs add-ons
  • Show screenshot of Labs → Lite/Pro upgrade state (highlight the old add-ons that can be deleted)
  • Show screenshot of Lite/Pro state going forward
• Upgrade Troubleshooting
  • Add-on system in JIRA is a fickle beast. We tried our best to make this upgrade as smooth as possible, but even so sometimes depending on your exact setup things can go wrong
  • Pages don't load (like getting started, automation rule config):
    • Uninstall old Labs add-ons "Automation module" and "JIRA AUtomation SPI" (check)
    • Try disabling/enabling Automation for JIRA
    • Try restarting JIRA
  • Third party actions (like "Midori's Attach PDF") no longer work with audit log errors or errors when configuring rules:
    • Uninstall old Labs add-ons "Automation module" and "JIRA AUtomation SPI" (check)
    • Try disabling/enabling Automation for JIRA
    • Try disabling/enabling Third party extension
    • Try restarting JIRA

Who this guide is for

This guide only concerns users who are looking to upgrade from the old Atlassian Labs "Automation Lite for JIRA Server" (formerly "JIRA Automation") add-on to the new "Automation for JIRA" (either Lite or Pro) add-on provided by Code Barrel. This guide is only required for JIRA Server.  If you are in Cloud, you can safely ignore this page.  

For a full breakdown of the differences between the different Automation for JIRA editions, please see Automation Lite vs Automation for JIRA.

Upgrade scenarios

There's a number of different upgrade scenarios to consider:

...

Automation Lite for JIRA Server v2.0.3
provided by Atlassian Labs
(also called "JIRA Automation")

...

This upgrade will be offered for free via the 'Manage add-ons' section in JIRA. It's the most common upgrade path for current users of the free offering

...

Simply upgrade the "Automation Lite for JIRA Server" add-on via the 'Manage add-ons' section in JIRA

...

This upgrade path is for users wishing to switch directly to our paid offering from the current free Labs offering

...

Simply install the "Automation for JIRA" add-on via the 'Manage add-ons' section in JIRA

...

Please note, that all your existing automation rules will be migrated in every upgrade scenario.  So for example if you have some automation rules configured in "Automation Lite for JIRA Server" and install the Pro edition, then all your automation rules will be migrated across.

Third part Automation extensions

A final scenario to consider is if you are using third party extensions to Automation for JIRA, such as Midori's PDF Automation add-on, or Valiantys' nFeeds add-on.  We continue to provide support for these third party extensions, however the configuration UI has changed significantly and these third party extensions will have to be updated with the new UI. We're actively working with vendors to provide new versions of their add-ons soon, but in the meantime we will render a fallback UI that should still allow you to use these extensions.  Rules already configured with actions provided by third party extensions will continue to run.

Add-ons provided by the different editions in 'Manage add-ons'