Upgrading Automation for Jira

• If you used Automation for Jira before, you might need to complete pre-upgrade steps before using this app. Learn more

Release notes

• For the list of all changes and new features, see Automation for Jira release notes.

Upgrading Automation for Jira

• If you used Automation for Jira before, you might need to complete pre-upgrade steps before using this app. Learn more

Release notes

• For the list of all changes and new features, see Automation for Jira release notes.

Upgrading Automation for Jira

• If you used Automation for Jira before, you might need to complete pre-upgrade steps before using this app. Learn more

Release notes

• For the list of all changes and new features, see Automation for Jira release notes.

Upgrading Automation for Jira

• If you used Automation for Jira before, you might need to complete pre-upgrade steps before using this app. Learn more

Release notes

• For the list of all changes and new features, see Automation for Jira release notes.

Upgrading Automation for Jira

• If you used Automation for Jira before, you might need to complete pre-upgrade steps before using this app. Learn more

Release notes

• For the list of all changes and new features, see Automation for Jira release notes.

Upgrading Automation for Jira

• If you used Automation for Jira before, you might need to complete pre-upgrade steps before using this app. Learn more

Release notes

• For the list of all changes and new features, see Automation for Jira release notes.

Upgrading Automation for Jira

• If you used Automation for Jira before, you might need to complete pre-upgrade steps before using this app. Learn more

Release notes

• For the list of all changes and new features, see Automation for Jira release notes.

Upgrading Automation for Jira

• If you used Automation for Jira before, you might need to complete pre-upgrade steps before using this app. Learn more

Release notes

• For the list of all changes and new features, see Automation for Jira release notes.

Upgrading Automation for Jira

• If you used Automation for Jira before, you might need to complete pre-upgrade steps before using this app. Learn more

Release notes

• For the list of all changes and new features, see Automation for Jira release notes.

Upgrading Automation for Jira

• If you used Automation for Jira before, you might need to complete pre-upgrade steps before using this app. Learn more

Release notes

• For the list of all changes and new features, see Automation for Jira release notes.

Upgrading Automation for Jira

• If you used Automation for Jira before, you might need to complete pre-upgrade steps before using this app. Learn more

Release notes

• For the list of all changes and new features, see Automation for Jira release notes.

Upgrading Automation for Jira

• If you used Automation for Jira before, you might need to complete pre-upgrade steps before using this app. Learn more

Release notes

• For the list of all changes and new features, see Automation for Jira release notes.

Upgrading Automation for Jira

• If you used Automation for Jira before, you might need to complete pre-upgrade steps before using this app. Learn more

Release notes

• For the list of all changes and new features, see Automation for Jira release notes.

Upgrading Automation for Jira

• If you used Automation for Jira before, you might need to complete pre-upgrade steps before using this app. Learn more

Release notes

• For the list of all changes and new features, see Automation for Jira release notes.

Upgrading Automation for Jira

• If you used Automation for Jira before, you might need to complete pre-upgrade steps before using this app. Learn more

Release notes

• For the list of all changes and new features, see Automation for Jira release notes.

Upgrading Automation for Jira

• If you used Automation for Jira before, you might need to complete pre-upgrade steps before using this app. Learn more

Release notes

• For the list of all changes and new features, see Automation for Jira release notes.

Upgrading Automation for Jira

• If you used Automation for Jira before, you might need to complete pre-upgrade steps before using this app. Learn more

Release notes

• For the list of all changes and new features, see Automation for Jira release notes.

Upgrading Automation for Jira

• If you used Automation for Jira before, you might need to complete pre-upgrade steps before using this app. Learn more

Release notes

• For the list of all changes and new features, see Automation for Jira release notes.

Upgrading Automation for Jira

• If you used Automation for Jira before, you might need to complete pre-upgrade steps before using this app. Learn more

Release notes

• For the list of all changes and new features, see Automation for Jira release notes.

Upgrading Automation for Jira

• If you used Automation for Jira before, you might need to complete pre-upgrade steps before using this app. Learn more

Release notes

• For the list of all changes and new features, see Automation for Jira release notes.

Upgrading Automation for Jira

• If you used Automation for Jira before, you might need to complete pre-upgrade steps before using this app. Learn more

Release notes

• For the list of all changes and new features, see Automation for Jira release notes.

Upgrading Automation for Jira

• If you used Automation for Jira before, you might need to complete pre-upgrade steps before using this app. Learn more

Release notes

• For the list of all changes and new features, see Automation for Jira release notes.

Upgrading Automation for Jira

• If you used Automation for Jira before, you might need to complete pre-upgrade steps before using this app. Learn more

Release notes

• For the list of all changes and new features, see Automation for Jira release notes.

Upgrading Automation for Jira

• If you used Automation for Jira before, you might need to complete pre-upgrade steps before using this app. Learn more

Release notes

• For the list of all changes and new features, see Automation for Jira release notes.

Upgrading to Automation for Jira 7.4

Before you upgrade, you need to complete prerequisite steps and might also need to download and run scripts on your database if you’re using MySQL or SQL Server.

Not completing these steps can break your upgrade.

For more info, see Upgrading to Automation for Jira 7.3 and newer..

Release notes

For the list of all changes and new features, see Automation for Jira release notes.

Upgrading to Automation for Jira 7.4

Before you upgrade, you need to complete prerequisite steps and might also need to download and run scripts on your database if you’re using MySQL or SQL Server.

Not completing these steps can break your upgrade.

For more info, see Upgrading to Automation for Jira 7.3 and newer..

Release notes

For the list of all changes and new features, see Automation for Jira release notes.

Upgrading to Automation for Jira 7.4

Before you upgrade, you need to complete prerequisite steps and might also need to download and run scripts on your database if you’re using MySQL or SQL Server.

Not completing these steps can break your upgrade.

For more info, see Upgrading to Automation for Jira 7.3 and newer..

Release notes

For the list of all changes and new features, see Automation for Jira release notes.

Upgrading to Automation for Jira 7.4

Before you upgrade, you need to complete prerequisite steps and might also need to download and run scripts on your database if you’re using MySQL or SQL Server.

Not completing these steps can break your upgrade.

For more info, see Upgrading to Automation for Jira 7.3 and newer..

Release notes

For the list of all changes and new features, see Automation for Jira release notes.

Upgrading to Automation for Jira 7.4

Before you upgrade, you need to complete prerequisite steps and might also need to download and run scripts on your database if you’re using MySQL or SQL Server.

Not completing these steps can break your upgrade.

For more info, see Upgrading to Automation for Jira 7.3 and newer..

Release notes

For the list of all changes and new features, see Automation for Jira release notes.

Upgrading to Automation for Jira 7.4

Before you upgrade, you need to complete prerequisite steps and might also need to download and run scripts on your database if you’re using MySQL or SQL Server.

Not completing these steps can break your upgrade.

For more info, see Upgrading to Automation for Jira 7.3 and newer..

Release notes

For the list of all changes and new features, see Automation for Jira release notes.

Upgrading to Automation for Jira 7.3

Before you upgrade, you need to complete prerequisite steps and might also need to download and run scripts on your database if you’re using MySQL or SQL Server.

Not completing these steps can break your upgrade.

For more info, see Upgrading to Automation for Jira 7.3.

Release notes

For the list of all changes and new features, see Automation for Jira release notes.

Upgrading to Automation for Jira 7.3

Before you upgrade, you need to complete prerequisite steps and might also need to download and run scripts on your database if you’re using MySQL or SQL Server.

Not completing these steps can break your upgrade.

For more info, see Upgrading to Automation for Jira 7.3.

Release notes

For the list of all changes and new features, see Automation for Jira release notes.

Upgrading to Automation for Jira 7.3

Before you upgrade, you need to complete prerequisite steps and might also need to download and run scripts on your database if you’re using MySQL or SQL Server.

Not completing these steps can break your upgrade.

For more info, see Upgrading to Automation for Jira 7.3.

Release notes

For the list of all changes and new features, see Automation for Jira release notes.

Upgrading to Automation for Jira 7.3

Before you upgrade, you need to complete prerequisite steps and might also need to download and run scripts on your database if you’re using MySQL or SQL Server.

Not completing these steps can break your upgrade.

For more info, see Upgrading to Automation for Jira 7.3.

Release notes

For the list of all changes and new features, see Automation for Jira release notes.

Upgrading to Automation for Jira 7.3

Before you upgrade, you need to complete prerequisite steps and might also need to download and run scripts on your database if you’re using MySQL or SQL Server.

Not completing these steps can break your upgrade.

For more info, see Upgrading to Automation for Jira 7.3.

Release notes

For the list of all changes and new features, see Automation for Jira release notes.

Upgrading to Automation for Jira 7.3

Before you upgrade, you need to complete prerequisite steps and might also need to download and run scripts on your database if you’re using MySQL or SQL Server.

Not completing these steps can break your upgrade.

For more info, see Upgrading to Automation for Jira 7.3.

Release notes

For the list of all changes and new features, see Automation for Jira release notes.

Issues fixed in this release:

No issue keys found since last release. Please update these release notes!

Various bug fixes and improvements.

Issues fixed in this release:

Rule actor locale ensured in rule execution.

Added configuration (tenant property 'ms.teams.notification.action.url.prefix') for Microsoft Teams messages webhook URL prefix customisation.

Fixed formatting in sidebar condition block summary.

Other various fixes and improvements.

Issues fixed in this release:

Rule actor locale ensured in rule execution.

Added configuration (tenant property 'ms.teams.notification.action.url.prefix') for Microsoft Teams messages webhook URL prefix customisation.

Fixed formatting in sidebar condition block summary.

Other various fixes and improvements.

Issues fixed in this release:

Limited jira log file pollution when rule stats are calculated.

Fixed 3rd party API implemented component execution with multiple queued items.

JSD to JSM rebranding.

Issues fixed in this release:

Limited jira log file pollution when rule stats are calculated.

Fixed 3rd party API implemented component execution with multiple queued items.

JSD to JSM rebranding.

Improved integration with Atlassian Insight REST API v8.4 and greater.

Added loading archived projects' details for projects having rules assigned to them, so their names nad keys will be displayed in the rule list.

Changed rule import process. Now, failure to parse single rule won't stop entire import.

Improved outgoing webhook action processing and its impact on rule state.

Improved user validation in User Condition.

Improved integration with Atlassian Insight REST API v8.4 and greater.

Added loading archived projects' details for projects having rules assigned to them, so their names nad keys will be displayed in the rule list.

Changed rule import process. Now, failure to parse single rule won't stop entire import.

Improved outgoing webhook action processing and its impact on rule state.

Improved user validation in User Condition.

Fixed save operation of a rule, that uses issue assign action with user limited to selected group.

Fixed compatibility with Atlassian Insight plugin.

Added new configuration property: "user.condition.get.users.limit" for setting the maximum number of users handled in specific 'user in role' condition.

Date handling improved for Create Version and Release Version actions.

Fixed save operation of a rule, that uses issue assign action with user limited to selected group.

Fixed compatibility with Atlassian Insight plugin.

Added new configuration property: "user.condition.get.users.limit" for setting the maximum number of users handled in specific 'user in role' condition.

Date handling improved for Create Version and Release Version actions.

Added support for Atlassian Insight plugin version 8.4 and higher.

Restored export/import compatibility of Issue fields condition with Automation for Jira Cloud.

Added support for Atlassian Insight plugin version 8.4 and higher.

Restored export/import compatibility of Issue fields condition with Automation for Jira Could.

Re-enabled epic link support in field value change trigger.

Provided alternative avatar icon for missing project avatars in rule list.

Fixed CDN compatibility issue in Jira Data Center.

Slack service URL prefix could be changed via tenant property named slack.notification.action.url.prefix.

Re-enabled epic link support in field value change trigger.

Provided alternative avatar icon for missing project avatars in rule list.

Slack service URL prefix could be changed via tenant property named slack.notification.action.url.prefix.

Added smart values support for Jira ServiceDesk customer feedback rate {{issue.Satisfaction.rate}}, and feedback scale {{issue.Satisfaction.scale}}.

Added configuration property outgoing.webhook.timeout.ms to setup request timeout.

Added smart values aggregate functions (sum, avg, max, min) valid for number properties of collection.

Various bug fixes and improvements.

Added smart values support for Jira ServiceDesk customer feedback rate {{issue.Satisfaction.rate}}, and feedback scale {{issue.Satisfaction.scale}}.

Added configuration property outgoing.webhook.timeout.ms to setup request timeout.

Added smart values aggregate functions (sum, avg, max, min) valid for number properties of collection.

Various bug fixes and improvements.

Various bug fixes and improvements

Various bug fixes and improvements

Issues fixed in this release:

JIRAAUTOSERVER-32 - We've fixed an issue that resulted in poor database query performance on the "AO589059RULE_STAT" table. This version is a recommended upgrade for large instances of Jira running many automation rules. AUT-1899 - Edit issue now provides a warning when editing issue types (related to differing workflows)

Issues fixed in this release:

JIRAAUTOSERVER-32 - We've fixed an issue that resulted in poor database query performance on the "AO589059RULE_STAT" table. This version is a recommended upgrade for large instances of Jira running many automation rules. AUT-1899 - Edit issue now provides a warning when editing issue types (related to differing workflows)

We broke the lite version in our last release - sorry. Here comes the fix!

We broke the lite version in our last release - sorry. Here comes the fix!

Minor bug fixes.

Minor bug fixes.

Issues fixed in this release:

• AUT-1776 - Error in "to" field for send email action do not yield "Some errors" status for rule execution
• AUT-1246 - Add support for plus/minus Business Hours/Minutes
• AUT-1913 - THROTTLED rule_stat state not tracked when it occurs during triggering
• AUT-947 - businessDaysBetween / days between functions should be able to return negative days
• AUT-605 - Allow for greater than and less than to the "Advanced Compare to" condition
• AUT-1901 - Onboarding to new rules should only show when you're creating your first rule

Issues fixed in this release:

• AUT-1776 - Error in "to" field for send email action do not yield "Some errors" status for rule execution
• AUT-1246 - Add support for plus/minus Business Hours/Minutes
• AUT-1913 - THROTTLED rule_stat state not tracked when it occurs during triggering
• AUT-947 - businessDaysBetween / days between functions should be able to return negative days
• AUT-605 - Allow for greater than and less than to the "Advanced Compare to" condition
• AUT-1901 - Onboarding to new rules should only show when you're creating your first rule

Jira 8.8 support and several bug fixes and a few new features.

Issues fixed in this release:

• AUT-1909 - Support for Jira 8.8.0
• AUT-310 - Add Groups & Roles to Assign action
• AUT-205 - More powerful User Condition
• AUT-204 - Outgoing webhook should be able to send any type of HTTP request (GET, etc)
• AUT-1780 - Add a "Send sample request" function to the send webhook action
• AUT-1900 - Users can get an email notification on when limits breached/close
• AUT-1809 - Issue condition to support empty / not empty checks for sprint field
• AUT-1466 - Smart-value - iterate over list in reverse order
• AUT-1863 - Multi group picker intermittently clears typed text

Jira 8.8 support and several bug fixes and a few new features.

Issues fixed in this release:

• AUT-1909 - Support for Jira 8.8.0
• AUT-310 - Add Groups & Roles to Assign action
• AUT-205 - More powerful User Condition
• AUT-204 - Outgoing webhook should be able to send any type of HTTP request (GET, etc)
• AUT-1780 - Add a "Send sample request" function to the send webhook action
• AUT-1900 - Users can get an email notification on when limits breached/close
• AUT-1809 - Issue condition to support empty / not empty checks for sprint field
• AUT-1466 - Smart-value - iterate over list in reverse order
• AUT-1863 - Multi group picker intermittently clears typed text

Issues fixed in this release:

• AUT-1904 - Server Lite - Global rules can't be saved
• AUT-165 - Add ability to delete a comment
• UI improvements.

Issues fixed in this release:

• AUT-1904 - Server Lite - Global rules can't be saved
• AUT-165 - Add ability to delete a comment
• UI improvements.

Implemented month time range for performance insights.

Issues fixed in this release:

• AUT-1889 - Performance insights in server having issues with UTC times due to rule_stat using system time

Implemented month time range for performance insights.

Issues fixed in this release:

• AUT-1889 - Performance insights in server having issues with UTC times due to rule_stat using system time

Issues fixed in this release:

• AUT-1882 - Not possible to use Delete Issue link(s) Action if link type not selected
• AUT-1887 - Unable to edit time tracking fields from simple fields list
• AUT-1858 - Create Service Desk Request broken in Server
• AUT-1860 - Jira CreateProject API has been updated

Issues fixed in this release:

• AUT-1882 - Not possible to use Delete Issue link(s) Action if link type not selected
• AUT-1887 - Unable to edit time tracking fields from simple fields list
• AUT-1858 - Create Service Desk Request broken in Server
• AUT-1860 - Jira CreateProject API has been updated

Issues fixed in this release:

• AUT-1876 - Add compatibility with Jira 8.7.1 for server
• AUT-1861 - Unable to use Japanese characters in the "From name" in email

Issues fixed in this release:

• AUT-1876 - Add compatibility with Jira 8.7.1 for server
• AUT-1861 - Unable to use Japanese characters in the "From name" in email

Issues fixed in this release:

• AUT-1854 - SLA rules should show more information about the SLA in the dropdown, and should filter based on rule scope
• AUT-1800 - Add project association to performance insights
• AUT-1844 - Allow for multi group picker fields to work as a smart value for the User condition

Issues fixed in this release:

• AUT-1854 - SLA rules should show more information about the SLA in the dropdown, and should filter based on rule scope
• AUT-1800 - Add project association to performance insights
• AUT-1844 - Allow for multi group picker fields to work as a smart value for the User condition

Issues fixed in this release:

• AUT-1836 - Unable to set a update the Sprint field
• AUT-1838 - Ensure we're compatible with Jira Server 8.6/8.6.1

Issues fixed in this release:

• AUT-1836 - Unable to set a update the Sprint field
• AUT-1838 - Ensure we're compatible with Jira Server 8.6/8.6.1

Issues fixed in this release:

Resolves bug on the rule list in Automation for Jira Lite Server version 7.0.8.

Issues fixed in this release:

Resolves bug on the rule list in Automation for Jira Lite Server version 7.0.8.

Issues fixed in this release:

• AUT-1093 - Update version should support the same project selector as create version
• AUT-1691 - Contains option for multi select fields in issue condition is misleading, consider renaming
• AUT-1836 - Unable to set a update the Sprint field
• AUT-1833 - Create issue action is missing parent drop down for sub tasks
• AUT-1382 - Removing entire 'else-if' block from rule doesn't put rule back into 'Draft' mode so can't be saved
• AUT-1753 - "Create Service Desk request" can hang forever
• AUT-938 - Allow the Edit action to edit the trigger issue when in a branch

Issues fixed in this release:

• AUT-1093 - Update version should support the same project selector as create version
• AUT-1691 - Contains option for multi select fields in issue condition is misleading, consider renaming
• AUT-1836 - Unable to set a update the Sprint field
• AUT-1833 - Create issue action is missing parent drop down for sub tasks
• AUT-1382 - Removing entire 'else-if' block from rule doesn't put rule back into 'Draft' mode so can't be saved
• AUT-1753 - "Create Service Desk request" can hang forever
• AUT-938 - Allow the Edit action to edit the trigger issue when in a branch

Issues fixed in this release:

• AUT-1819 - String smart-value functions like replace, replaceAll broken in latest server release (7.0.3)

Issues fixed in this release:

• AUT-1819 - String smart-value functions like replace, replaceAll broken in latest server release (7.0.3)

Issues fixed in this release:

• AUT-1753 - "Create Service Desk request" can hang forever
• AUT-1666 - Can't click validate issues on scheduled trigger when "Only Include issues" is unchecked

Issues fixed in this release:

• AUT-1753 - "Create Service Desk request" can hang forever
• AUT-1666 - Can't click validate issues on scheduled trigger when "Only Include issues" is unchecked

Issues fixed in this release:

• AUT-1805 - Import rules is not working in cloud
• AUT-1799 - Content type header checking should not be case sensitive for the web request response handling
• AUT-1777 - Ability to access sprint goal via smart value (for issue)

Issues fixed in this release:

• AUT-1805 - Import rules is not working in cloud
• AUT-1799 - Content type header checking should not be case sensitive for the web request response handling
• AUT-1777 - Ability to access sprint goal via smart value (for issue)

Issues fixed in this release:

• AUT-1787 - Copy from sprint fields failing with NPE
• AUT-1743 - Add service customer with an existing email fails on cloud
• AUT-1733 - Server urls have a rogue "false" in them preventing copying urls and middle-clicking
• AUT-1426 - Permissions checks are not efficient in Cloud
• AUT-213 - Add action to delete links
• AUT-1749 - Ability to transfer from one user to another in Cloud & Server
• AUT-1540 - Document the fact that you can append (rather than replace) a component (or other field) without the need for advanced fields.

Issues fixed in this release:

• AUT-1787 - Copy from sprint fields failing with NPE
• AUT-1743 - Add service customer with an existing email fails on cloud
• AUT-1733 - Server urls have a rogue "false" in them preventing copying urls and middle-clicking
• AUT-1426 - Permissions checks are not efficient in Cloud
• AUT-213 - Add action to delete links
• AUT-1749 - Ability to transfer from one user to another in Cloud & Server
• AUT-1540 - Document the fact that you can append (rather than replace) a component (or other field) without the need for advanced fields.

Issues fixed in this release:

• AUT-1778 - Global Administration link on Project Admin view for A4J returns 404

Issues fixed in this release:

• AUT-1778 - Global Administration link on Project Admin view for A4J returns 404

This release introduces a new trigger - you can now run rules when issue links are deleted!

We've also fixed some other issues in this release:

• AUT-874 - Add a trigger on links being deleted
• AUT-1767 - Long horizontal text boxes auto scroll to the right when trying to type a value

This release introduces a new trigger - you can now run rules when issue links are deleted!

We've also fixed some other issues in this release:

• AUT-874 - Add a trigger on links being deleted
• AUT-1767 - Long horizontal text boxes auto scroll to the right when trying to type a value

Issues fixed in this release:

• AUT-1761 - Service Desk Request Type use to return the name and other fields when outputted, not it returns ServiceDeskRequestTypeFieldBean

Issues fixed in this release:

• AUT-1761 - Service Desk Request Type use to return the name and other fields when outputted, not it returns ServiceDeskRequestTypeFieldBean

Issues fixed in this release:

• AUT-1711 - Always look up the epic field by type rather than by possible name

Issues fixed in this release:

• AUT-1711 - Always look up the epic field by type rather than by possible name

Issues fixed in this release:

• AUT-1752 - Third party associated items can add null project ids to audit log context

Issues fixed in this release:

• AUT-1752 - Third party associated items can add null project ids to audit log context

Issues fixed in this release:

• AUT-1731 - Jira 7.13 resolution createmeta method not found
• AUT-1686 - Log work date picker is broken in both cloud & server
• AUT-1672 - Copying an empty field causes a "field are incompatible" error

Issues fixed in this release:

• AUT-1731 - Jira 7.13 resolution createmeta method not found
• AUT-1686 - Log work date picker is broken in both cloud & server
• AUT-1672 - Copying an empty field causes a "field are incompatible" error

New performance insights for rule statistics feature added to the "…" menu in both global and project admin.

Various improvements and fixes in this release:

• AUT-1732 - Issue condition is missing empty/not empty checks for Request Type
• AUT-1730 - Is empty/Is not empty check for Tempo Account is not working
• AUT-1729 - Assignable rest end point returning empty results through connect bridge
• AUT-456 - Expose rule statistics in the product

New performance insights for rule statistics feature added to the "…" menu in both global and project admin.

Various improvements and fixes in this release:

• AUT-1732 - Issue condition is missing empty/not empty checks for Request Type
• AUT-1730 - Is empty/Is not empty check for Tempo Account is not working
• AUT-1729 - Assignable rest end point returning empty results through connect bridge
• AUT-456 - Expose rule statistics in the product

Fixes a bug in assignee picker field (cloud only)

Fixes a bug in assignee picker field (cloud only)

Issues fixed in this release:

• AUT-1719 - Add audit ID to error notification email.
• AUT-1681 - Docs improvement: We're Platinum Vendor now!
• AUT-1706 - Single Version Field does not support Is Empty/Is Not Empty.

Issues fixed in this release:

• AUT-1719 - Add audit ID to error notification email.
• AUT-1681 - Docs improvement: We're Platinum Vendor now!
• AUT-1706 - Single Version Field does not support Is Empty/Is Not Empty.

Issues fixed in this release:

• AUT-1701 - Third party actions don't always load correctly

Issues fixed in this release:

• AUT-1701 - Third party actions don't always load correctly

Issues fixed in this release:

• AUT-1692 - Add ability to log webhook payload

Issues fixed in this release:

• AUT-1692 - Add ability to log webhook payload

Issues fixed in this release:

• AUT-1688 - Automation for Jira not compatible with Jira 8.4.0

Issues fixed in this release:

• AUT-1688 - Automation for Jira not compatible with Jira 8.4.0

Issues fixed in this release:

• AUT-1687 - AUTOMATION_QUEUE sql exception due to batch insert with generateKeys() (in MS SQLServer)

Issues fixed in this release:

• AUT-1687 - AUTOMATION_QUEUE sql exception due to batch insert with generateKeys() (in MS SQLServer)

Issues fixed in this release:

• AUT-1680 - Referencing a smart-value property on a wrapped object in a collection doesn't work

Issues fixed in this release:

• AUT-1680 - Referencing a smart-value property on a wrapped object in a collection doesn't work

Issues fixed in this release:

• AUT-1675 - Ignore null map keys when serialising issue JSON in server
• AUT-1658 - React select sometimes renders x as ×

Issues fixed in this release:

• AUT-1675 - Ignore null map keys when serialising issue JSON in server
• AUT-1658 - React select sometimes renders x as ×

Issues fixed in this release: Our most voted for feature ever - The ability to render wiki markup as HTML and/or extract text only from wiki markup.

Dealing with wiki markup

• AUT-497 - Provide access to text & rendered representation of fields
• AUT-1647 - Docs Improvement - Tempo Smart Value can be misleading
• AUT-1669 - Add how to use smart values in Bulk handling section

Issues fixed in this release: Our most voted for feature ever - The ability to render wiki markup as HTML and/or extract text only from wiki markup.

Dealing with wiki markup

• AUT-497 - Provide access to text & rendered representation of fields
• AUT-1647 - Docs Improvement - Tempo Smart Value can be misleading
• AUT-1669 - Add how to use smart values in Bulk handling section

Issues fixed in this release:

• AUT-1668 - Automation for Jira 6.0.7 fails to enable in older versions of Jira
• AUT-1573 - Server dead locks can occur due to audit log deletion being done in parallel

Issues fixed in this release:

• AUT-1668 - Automation for Jira 6.0.7 fails to enable in older versions of Jira
• AUT-1573 - Server dead locks can occur due to audit log deletion being done in parallel

Issues fixed in this release:

• AUT-1645 - NullPointer when asking for Request Type for non Service Desk issues
• AUT-1533 - Using smart value to set the Fix Version field in Create issue action after trigger a rule when a Version is created

Issues fixed in this release:

• AUT-1645 - NullPointer when asking for Request Type for non Service Desk issues
• AUT-1533 - Using smart value to set the Fix Version field in Create issue action after trigger a rule when a Version is created

Issues fixed in this release:

• AUT-1614 - Do not send error emails to inactive users
• AUT-1628 - RequestType doesn't remove duplicates for the IssueCondition when in a global rule
• AUT-1618 - RequestType querying does not work in server for a project specific rule
• AUT-1533 - Using smart value to set the Fix Version field in Create issue action after trigger a rule when a Version is created

Issues fixed in this release:

• AUT-1614 - Do not send error emails to inactive users
• AUT-1628 - RequestType doesn't remove duplicates for the IssueCondition when in a global rule
• AUT-1618 - RequestType querying does not work in server for a project specific rule
• AUT-1533 - Using smart value to set the Fix Version field in Create issue action after trigger a rule when a Version is created

Loop detection is now less strict, to fix some cases where loop detection would stop execution too soon. Now rules can call each other (or themselves) up to a depth of 10 times (which is configurable via our service limits).

We also fixed a bug where automation rules would stick around on project deletion.

Issues fixed in this release:

• AUT-923 - Event based loop detection "Issue event trigger detected possible loop. Two successive executions against same issue:" is too strict
• AUT-1054 - When a project is deleted all it's project rules should also be deleted.

Loop detection is now less strict, to fix some cases where loop detection would stop execution too soon. Now rules can call each other (or themselves) up to a depth of 10 times (which is configurable via our service limits).

We also fixed a bug where automation rules would stick around on project deletion.

Issues fixed in this release:

• AUT-923 - Event based loop detection "Issue event trigger detected possible loop. Two successive executions against same issue:" is too strict
• AUT-1054 - When a project is deleted all it's project rules should also be deleted.

Issues fixed in this release:

• AUT-1612 - Edit Issue action is not listing Sprints on A4J 6.0.1 - Project Automation and Global Administration sections (also Sprint trigger board picker)

Issues fixed in this release:

• AUT-1612 - Edit Issue action is not listing Sprints on A4J 6.0.1 - Project Automation and Global Administration sections (also Sprint trigger board picker)

We had a mistake in our licensing logic, that meant Automatin for Jira would stop working for customers running with a server app licenses in Jira Data Center instances from the 10th of September 2019.

We've also fixed a number of bugs:

• AUT-990 - Certain fields may not be accessible in smart-values depending on the permissions/roles of the user who triggered the event
• AUT-1072 - Unable to select "Same status (loop)" in transition action
• AUT-1420 - For parent related branch should ignore issues that are not sub-tasks (check other related options too)
• AUT-1603 - Lookup request type field by type instead of label when resolving urls
• AUT-1600
• AUT-1580 - Audit log entries are often not in the correct order
• AUT-1599 - Our docs are referring to {{{{#issues.size}}}} to get the count of issues.
• AUT-1605 - Copying and pasting from the docs may cause smart values to not render
• AUT-1387 - Add warning that multiple issue event matches specific events only

We had a mistake in our licensing logic, that meant Automatin for Jira would stop working for customers running with a server app licenses in Jira Data Center instances from the 10th of September 2019.

We've also fixed a number of bugs:

• AUT-990 - Certain fields may not be accessible in smart-values depending on the permissions/roles of the user who triggered the event
• AUT-1072 - Unable to select "Same status (loop)" in transition action
• AUT-1420 - For parent related branch should ignore issues that are not sub-tasks (check other related options too)
• AUT-1603 - Lookup request type field by type instead of label when resolving urls
• AUT-1600
• AUT-1580 - Audit log entries are often not in the correct order
• AUT-1599 - Our docs are referring to {{{{#issues.size}}}} to get the count of issues.
• AUT-1605 - Copying and pasting from the docs may cause smart values to not render
• AUT-1387 - Add warning that multiple issue event matches specific events only

In this release (v6.0.0) of Automation for Jira we are introducing the brand new third party extensions API.

With this new API, Marketplace vendors will be able to provide much more powerful extensions for Automation for Jira, including pluggable triggers, conditions and actions!

For more details on how to get started with extensions, please see our release blog!

This release is 100% backwards compatible - all your existing rules and extensions will continue to function. Enjoy!

In this release (v6.0.0) of Automation for Jira we are introducing the brand new third party extensions API.

With this new API, Marketplace vendors will be able to provide much more powerful extensions for Automation for Jira, including pluggable triggers, conditions and actions!

For more details on how to get started with extensions, please see our release blog!

This release is 100% backwards compatible - all your existing rules and extensions will continue to function. Enjoy!

Issues fixed in this release:

• AUT-1397 - Investigate/Fix the missing actions in the rule playground
• AUT-582 - Add a "Destination issue" as an option in the branch block
• AUT-1470 - Add date function to set "Day of week"
• AUT-1594 - Copy from destination issue
• AUT-1566 - JQL issue condition link navigates to a broken component when it contains an existing JQL statement
• AUT-1476 - Update sprint field placeholder text to say leaving blank will clear value
• AUT-1537 - Typo in description of 'Release Version' Action (in product)
• AUT-1588 - Issue Field Component picker broken in project config
• AUT-1398 - Unable to use smart values in Edit action's user fields

Issues fixed in this release:

• AUT-1397 - Investigate/Fix the missing actions in the rule playground
• AUT-582 - Add a "Destination issue" as an option in the branch block
• AUT-1470 - Add date function to set "Day of week"
• AUT-1594 - Copy from destination issue
• AUT-1566 - JQL issue condition link navigates to a broken component when it contains an existing JQL statement
• AUT-1476 - Update sprint field placeholder text to say leaving blank will clear value
• AUT-1537 - Typo in description of 'Release Version' Action (in product)
• AUT-1588 - Issue Field Component picker broken in project config
• AUT-1398 - Unable to use smart values in Edit action's user fields

Issues fixed in this release:

• AUT-1559 - Project picker in issue condition broken on server

Issues fixed in this release:

• AUT-1559 - Project picker in issue condition broken on server

Issues fixed in this release:

• AUT-1555 - Investigate why issue condition uses "global scope" for composite lookups in an if/else block
• AUT-1563 - New logic to filter sprints by getOriginBoardId is too strict
• AUT-1562 - Be more defensive with "?" emails.
• AUT-1561 - Waiting for response for Send Web Request fails if inside an if/else block
• AUT-1485 - Component Field support in the Issue Condition

Issues fixed in this release:

• AUT-1555 - Investigate why issue condition uses "global scope" for composite lookups in an if/else block
• AUT-1563 - New logic to filter sprints by getOriginBoardId is too strict
• AUT-1562 - Be more defensive with "?" emails.
• AUT-1561 - Waiting for response for Send Web Request fails if inside an if/else block
• AUT-1485 - Component Field support in the Issue Condition

The Issue Fields Condition supports some new fields - you can now match based on labels and version fields! Text fields now also support case sensitive matches. Enjoy!

Issues fixed in this release:

• AUT-1551 - Tempo field in cloud doesn't accept smart-values
• AUT-1547 - Show deleted projects in rule restriction so they can be removed
• AUT-1525 - Add support for version fields in the issue condition
• AUT-1519 - Cases insensitive option for text comparisons in issue condition
• AUT-1484 - Label field support in the Issue Condition

The Issue Fields Condition supports some new fields - you can now match based on labels and version fields! Text fields now also support case sensitive matches. Enjoy!

Issues fixed in this release:

• AUT-1551 - Tempo field in cloud doesn't accept smart-values
• AUT-1547 - Show deleted projects in rule restriction so they can be removed
• AUT-1525 - Add support for version fields in the issue condition
• AUT-1519 - Cases insensitive option for text comparisons in issue condition
• AUT-1484 - Label field support in the Issue Condition

Added multi select field and checkbox support for issue condition field.

Issues included in this release:

• AUT-1469 - Issue condition: Summary Input for text field shouldn't use "summary" as the name
• AUT-1394 - Improve documentation around user properties and legacy user properties
• AUT-1516 - Add support for multi value select custom fields

Added multi select field and checkbox support for issue condition field.

Issues included in this release:

• AUT-1469 - Issue condition: Summary Input for text field shouldn't use "summary" as the name
• AUT-1394 - Improve documentation around user properties and legacy user properties
• AUT-1516 - Add support for multi value select custom fields

Issues fixed in this release:

• AUT-1529 - Changelog enricher can break in server
• AUT-1505 - Condition type searches should be case insensitive
• AUT-1514 - Active sprints can return from multiple boards depending on the board filter in Cloud
• AUT-1501 - Support basic functionality for multi-user fields in the issue condition
• AUT-1512 - Service limit breached trigger broken with JS error
• AUT-1508 - Custom single select summary display for arrays is wrong

Issues fixed in this release:

• AUT-1529 - Changelog enricher can break in server
• AUT-1505 - Condition type searches should be case insensitive
• AUT-1514 - Active sprints can return from multiple boards depending on the board filter in Cloud
• AUT-1501 - Support basic functionality for multi-user fields in the issue condition
• AUT-1512 - Service limit breached trigger broken with JS error
• AUT-1508 - Custom single select summary display for arrays is wrong

Issues fixed in this release:

• AUT-1509 - Date time picker doesn't support smart-values
• AUT-1497 - Provide single user field support in Issue Condition
• AUT-1502 - Add support for custom single select fields
• AUT-1496 - Include initiator as part of the parameters passed to custom third party actions

Issues fixed in this release:

• AUT-1509 - Date time picker doesn't support smart-values
• AUT-1497 - Provide single user field support in Issue Condition
• AUT-1502 - Add support for custom single select fields
• AUT-1496 - Include initiator as part of the parameters passed to custom third party actions

Our new issue field condition allows you to easily put a condition together without needing to write smart values or JQL. You just click what you want from our populated drop-downs and fill in the blanks.

• AUT-1427 - Send WebHook/Web Request action should include error message when it fails
• AUT-632 - Add a warning to edit 'Issue type' to indicate this can cause issues when changing workflows

Our new issue field condition allows you to easily put a condition together without needing to write smart values or JQL. You just click what you want from our populated drop-downs and fill in the blanks.

• AUT-1427 - Send WebHook/Web Request action should include error message when it fails
• AUT-632 - Add a warning to edit 'Issue type' to indicate this can cause issues when changing workflows

Various bug fixes

• AUT-1456 - json Encoding not thread safe
• AUT-1422 - Translation bug with 'Epic' of an issue - again
• AUT-1415 - System field keys should be case insensitive
• AUT-1433 - Customfield called Properties causes errors and weird behaviour
• AUT-1379 - Not all boards available in sprint picker for global rules

Various bug fixes

• AUT-1456 - json Encoding not thread safe
• AUT-1422 - Translation bug with 'Epic' of an issue - again
• AUT-1415 - System field keys should be case insensitive
• AUT-1433 - Customfield called Properties causes errors and weird behaviour
• AUT-1379 - Not all boards available in sprint picker for global rules

Minor improvement to add hovers for truncated multi-select values

• AUT-1355 - Provide full name of options in multi select, auto complete on hover

Minor improvement to add hovers for truncated multi-select values

• AUT-1355 - Provide full name of options in multi select, auto complete on hover

Bug fix around smart values support for JQL trigger

• AUT-1429 - Scheduled trigger JQL doesn't support smart-values

Bug fix around smart values support for JQL trigger

• AUT-1429 - Scheduled trigger JQL doesn't support smart-values

This release contains a minor API compatibility fix.