...
A final scenario to consider is if you are using third party extensions to Automation for JIRA, such as the PDF Automation Plugin for JIRA by Midori or Valiantys' nFeeds add-on (see full list of extensions). 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.
...
When rules execute, the audit log might contain errors like "This rule component was provided by a third party add-on for Automation for JIRA. It appears this add-on is no longer installed or enabled." or the same error might be shown when trying to configure a rule. This means that during the upgrade somehow the third party add-ons providing these actions were disabled or not registered correctly.
You can find the full list of third party extensions in Automation Lite for JIRA here: Automation for JIRA third party extensions
Troubleshooting steps
- Uninstall the old labs add-ons "Automation module" and "JIRA Automation SPI" in the 'Manage add-on' section (but don't worry, you wont lose any data)
- Try disabling, then re-enabling Automation (Lite) for JIRA in the 'Manage add-on' section
- Try disabling, then re-enabling the third party extension add-ons in the 'Manage add-on' section
- If this didn't fix the problem: Try restarting JIRA
...