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-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-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-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

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)

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!

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-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

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-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

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

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.

Minor bug fixes

New feature: Access outgoing webhook response data in your rules

• AUT-1152 - Outgoing webhook should provide response data for subsequent rule components
• AUT-1340 - Update rest requests to not use the "latest" API

Fixed some UI related bugs

• AUT-1386 - User picker/group picker fields in user condition don't allow smart-values
• AUT-1380 - Multiple user conditions causes the criteria field to show an empty value
• AUT-1329 - Update Slack docs to indicate that you need to use user Ids rather than usernames
• AUT-1356 - Add summary of smart value support for Insight fields to the docs
• AUT-1354 - Styling of event type checkbox is off
• AUT-1359 - There is no way to remove a field from the edit action if it has been deleted or is no longer in the create/edit meta, it doesn't show up but it remains in the rule

Fix for edit comment event picked up by 'Issue commented' rules

• AUT-1377 - Comment edited event triggers 'Issue commented' rules
• AUT-1376 - NPE due to null e-mails of users in servicedesk orgs

Added support for copying and editing Tempo accounts in the Create/Edit/Transition actions

• AUT-392 - Add support for Tempo 'Account' field to simple form
• AUT-1326 - We should ignore screen checks for create and transition in Server
• AUT-1342 - Small Typo in new Set 'From name' for send email.

Minor performance improvement for instances with lots of users

AUT-1353 - Tenant Info shouldn't retrieve user count in server

• AUT-1339 - Rules are triggered twice when assignee field and multi user field are edited at the same time
• AUT-1346 - Publish event action results in duplicate invocation of listeners
• AUT-1349 - Component smart-values don't allow access to description field

Jira 8.0.1 introduced some API breakages that weren't present in Jira 8.0.0. This release fixes this compatibility problem.

• AUT-1344 - Automation for Jira is broken in Jira 8.0.1

We've improved our Send e-mail action in this release to support more recipient fields and allowing you to specify a 'From name'. E-mails will now also default to be sent by the default from address configured in Jira server (for new e-mail actions).

• AUT-1334 - Selecting smart-value in reporter field (and potentially others) causes blank page
• AUT-1318 - Improve warning around projectSafe param for third party extensions
• AUT-1165 - Ability to export a single rule
• AUT-281 - Set 'From name' for send email
• AUT-646 - Default From address in emails should be Jira's default in server
• AUT-745 - Add CC and BCC fields to email action
• AUT-714 - Transition Action: Selecting same transition twice, hides all other transitions.
• AUT-1296 - Improve error reporting around plugin modules not being available

We've fixed a few gnarly bugs around publishing custom events and rules triggered by field changes to the assignee field.

• AUT-1305 - When assigning an issue, field value changed rules trigger twice
• AUT-1309 - Send Webhook Docs don't mention all fields that support smart values
• AUT-1193 - Re-name 'Refresh issues' to 'Re-fetch issues' in our docs
• AUT-1291 - Add documentation for version smart value for version triggers
• AUT-1303 - Multiple issue event trigger is broken with custom events in Automation 5.1.x

We've added support to edit original and remaining estimate fields on issues now. This release also includes a number of bug fixes:

• AUT-1294 - Issue commented rules triggering twice when assigning issue with comment
• AUT-1284 - Jira software 7.4.0 Sprint triggers break in Automation for Jira
• AUT-329 - Add time tracking fields to edit/create/transition
• AUT-1293 - Issue parent not accessible in rules triggered by "Issue created" since 5.1.0
• AUT-1292 - MD5 hash for automation event uses wrong character encoding

We've fixed a gnarly bug introduced in 5.1.0 in this release that meant for some workflows, 'Issue created' rules wouldn't trigger anymore (in particular if they contained 'assign' post-functions in their initial transition).

• AUT-1287 - Create issue event based rules not triggering in Automation for Jira 5.1.0
• AUT-1279 - Automation UI is freezing browser tab for specific version and environment

Fixed bug with entity properties API breakage in Jira 7.x

• AUT-1267 - Automation for Jira 5.0.0 breaks entity property lookups in Jira 7.x
• AUT-1230 - Selecting a transition with a slash in the name results in a bad URL when loading the transition

We've added Jira 8 compatibility in this release. We also introduced a new action to allow you to log work on Jira issues in the pro version of Automation for Jira!

• AUT-1251 - Handle issue deleted/worklog deleted events better in Worklog trigger (pro only)
• AUT-1240 - The Field Value Changed trigger does not work for the 'comment' field
• AUT-1229 - Add work log action (pro only)

Bug fix for Server Schedules

• AUT-1263 - Optimistic lock for Scheduling can break in certain databases

Small bug fix

• AUT-1255 - {{comment.body}} can print out the whole comment history if there is no comment in the current context
• AUT-1227 - Update docs to use full text search
• AUT-1254 - Whitespace is trimmed as you type in new date fields

Fix for bug affecting user entity properties in smart-values

• AUT-1253 - User entity properties in smart-values in server not returning anything

Bug fix for failing Microsoft Teams notifications

• AUT-1252 - Provide better information when MS Teams API returns an error

We've fixed a number of smaller bugs in this release and made some engine room improvements to do with how users are identified internally.

• AUT-1247 - TimeTracking field does not include timespent
• AUT-1249 - Pretty Print for date diff doesn't return anything
• AUT-1242 - Edit issue action breaks in cloud with 'Automatic' option
• AUT-1167 - Invalid Resolution message when rule actor and rule owner are in different locales
• AUT-1147 - The add labels dialog gets chopped off when lots of labels

Added a trigger for when work is logged against an issue, bug fix for filtering rules and bug fix for allowing smart values in Raise a request on behalf of field when creating a Service Desk request

• AUT-1234 - Clicking on a rule after filtering rules maintains filter but clears text from input field
• AUT-1233 - Smart values not working in "Raise this request on behalf of"
• AUT-1223 - Add trigger for work logged events

You can now search for rules by keyword in the rule list. We've also fixed a bug with translated resolutions, that could stop the edit issue operation from working correctly.

• AUT-1167 - Invalid Resolution message when rule actor and rule owner are in different locales
• AUT-757 - Ability to filter rules by keyword

Fixes bug with starting a trial in lite

• AUT-1226 - Starting in-product pro trial on server yields a blank screen
• AUT-1222 - Cloud: When fetch to get list fields timesout we cache empty list of fields
• AUT-1224 - HttpClientImpl:104 Timeout sending request

zBug fix for manage waters

• AUT-1221 - Setting the org by reporter email doesn't find orgs when you select option to not create
• AUT-1215 - Server manage watchers is broken for renamed usernames
• AUT-1047 - Old user can stick around in the sidebar when switching assignees

We've fixed a few minor bugs in this release and include some internal engine room fixes to enable future work.

• AUT-1208 - Increase JQL timeouts to 60 seconds
• AUT-1199 - User condition with multiple conditions displays accountIds in cloud

We've fixed a number of gnarly bugs in this release! Notably a performance problem with instances that had a large number of custom fields configured.

• AUT-1205 - Translations bug when copying priorities
• AUT-1204 - Performance problem when retrieving createMeta/editMeta in server
• AUT-1199 - User condition with multiple conditions displays accountIds in cloud
• AUT-1132 - Publishing a rule yields a blank screen
• AUT-1146 - Fix the i18n key shown when selecting 0 in SLA trigger
• AUT-454 - JQL Condition broken if contains ORDER BY clause

Bugfix

• AUT-1185 - "Only include recent issues..." checkbox in scheduled trigger can break JQL

We've fixed a translation bug with the Epic Link field, and some UI glitches with long text in the sidebar.

• AUT-415 - Hide text overflow after 3 lines in rule components in the sidebar
• AUT-1144 - Selecting a label in the rule list should clear the 'global' selection (if selected) since often you just end up with an empty list
• AUT-1179 - Translation bug with related issue branch not finding the 'Epic' of an issue

Fixing a bug around global configuration in Server Lite

• AUT-1180 - Global configuration UI is not available in server lite

In this release we've added anonymous usage statistics in server! For more details about why we're doing this, and what we're tracking, please see our blog.

We've also fixed a small bug with MS Teams:

• AUT-1178 - Send Microsoft Teams message is ignoring include issue summary and always including it

In this release we've added a new action to send MS Teams messages straight from Jira (see our blog for more)! We've also fixed a number of smaller bugs.

• AUT-1106 - Branching on created or most recently created when no issues have been created should log to the audit log
• AUT-415 - Hide text overflow after 3 lines in rule components in the sidebar
• AUT-72 - Microsoft Teams notifications
• AUT-748 - Retry Http requests when we receive a 502/503
• AUT-1100 - Global rules aren't shown on the Project Automation level until you add a project level rule
• AUT-1151 - Audit log sometimes works, sometimes shows an error screen for "All audit logs" screen
• AUT-766 - Allow smart values in outgoing webhook headers

This release resolves problems where in instances with a lot of rule executions MySQL could throw database deadlock exceptions when writing audit logs and rule statistics.

We also shipped a small improvement to outgoing webhooks to let you send HTTP requests using any method (PUT, GET, etc).

• AUT-1166 - MySQL default transaction level for Automation for Jira queries is wrong
• AUT-204 - Outgoing webhook should be able to send any type of HTTP request (GET, etc)

As of version 4.0.0, Automation Lite for Jira (the free version) is no longer supported in Jira Data Center. You can upgrade to our paid version to continue using Automation.

We also fixed a small bug in this release:

• AUT-1163 - Unable to edit a rule that has duplicate names in Global mode

As of version 4.0.0, Automation Lite for Jira (the free version) is no longer supported in Jira Data Center. You can upgrade to our paid version to continue using Automation.

We also fixed a small bug in this release:

• AUT-1163 - Unable to edit a rule that has duplicate names in Global mode

Trying to fix version incompatibility issues of previous deploy

Fix where the rule editor could result in a javascript error in rare cases

• AUT-1091 - JS Error - Add new component, moving the component, selecting action then type produces blank page

This release fixes a deadlock that can happen with MySQL under high load scenarios.

We've fixed a few bugs that could result in navigation problems when clicking certain links.

• AUT-1148 - "+ add regex to distinguish between multiple transitions to the same status" link on transition action is broken and jumps back to rule list
• AUT-1135 - Clicking 'Rule Details' when editing rule drops you back to rule list instead of rule details
• AUT-1133 - Audit log sometimes works, sometimes shows an error screen

Added support for browser navigation and lots of bug fixes, including a scheduling bug that could stop scheduled/polling rules running.

• AUT-1123 - Scheduler and Poller get deregistered
• AUT-1128 - Clicking 'cancel' on a new component routes to a blank screen
• AUT-1096 - Add description for "From" in Send Email to clarify
• AUT-1112 - Link mentioned issues sample rule regex is too broad
• AUT-974 - Browser history and bookmarking should work when navigating
• AUT-1060 - Sorting by project is broken
• AUT-981 - Comments action post JSD comments as Public unless the Send email flag is also set
• AUT-1069 - Both 'triggerissue' and 'triggerIssue' should work in smart-values
• AUT-1102 - Show all boards & epics in project specific boards
• AUT-1086 - Unable to access rule detail screen to change actor after copying a rule

JIRA 7.12 support

• AUT-1103 - Infinite loop when claiming items
• AUT-1089 - Send E-Mail action suggests smart value "{{ issue.fields.key }}" in help text, which is not a valid smart value
• AUT-959 - Event Type smart-value doesn't work in branches
• AUT-677 - Twillio checking credentials can throw error

We've updated some product logos to the latest in this release.

• AUT-1082 - Epic link field appears broken

We've fixed an issue where the Epic Link field would sometimes not work as expectd and Curly got a slight facelift in this version!

• AUT-1082 - Epic link field appears broken

Meet Curly, our new Automation robot! Curly has just finished the handover from trusty old Franky who's served us well over the years. Franky has automated 100 million rules in the last few years and a well-earned retirement beckons (she's been having this terrible pain in all the diodes down her left side if you must know :)

Fear not though, Automation for Jira isn't changing and still comes with all the same features as before. Read more on our blog.

We've also packed some bug fixes and features into this release:

• AUT-1094 - NullPointerException on VersionEventConverter if version is created anonymously
• AUT-877 - Add a status filter for the Transition trigger
• AUT-1073 - We should do delay rule checks for inlined Current Issue and if/else branches
• AUT-1078 - Copy rule with branch breaks UI

Enjoy!

We're bringing back Jira Data Center support in this release.

Bug fixes for Insight fields and picking Epics

• AUT-1076 - Can't extract summary from Insight field
• AUT-1068 - Unable to pick epics from boards that have non-project specific JQL

Bug fixes for service desk, webhooks and other various fixes.

• AUT-588 - SLA trigger should check if the SLA is paused before executing rule
• AUT-1000 - Resolution field: Should not be able to select "Unresolved" or bank as we don't support it
• AUT-1025 - In Server Base URL is cached at startup and wont reflect changes in Jira
• AUT-1010 - Outgoing email should put an entry in the audit log when no email addresses can be found
• AUT-973 - Clicking on the "else/if" block in the audit log renders a blank page
• AUT-983 - Delete attachments action regex shows error in UI when using valid Java regex instructions like (?i)
• AUT-971 - Map 'Customer Request Type' to 'Request type' in smart-values
• AUT-1065 - Increase outgoing webhook timeout to 5s and add more logging

Bug fix for handling masked email addresses

• AUT-1042 Allow users to disable creation of new organizations in "Set from reporter's email domain"
• AUT-1058 We should parse masked email addresses into proper emails
• AUT-1049 Incorrect error message for "Automation for Jira has exceeded"
• AUT-1053 Disable warning about the rule actor needing to be in the right group for comment visibility in cloud
• AUT-1050 Error badges no longer show up in the rule list

In this release we've updated all our user pickers to fix a number of different bugs.

• AUT-1043
• AUT-1033
• AUT-1044

We've fixed a bug in this release that broke sorting by different columns in the rule list.

• AUT-1034

Jira 7.11 support

• AUT-713 - Better validation of rules that require issues
• AUT-1012 - Disable rule processing while Jira indexing

We've fixed a number of bugs in this release:

• AUT-666
• AUT-970
• AUT-939
• AUT-1026
• AUT-744

• AUT-1022 - Caching bug for DataCenter
• AUT-1018 - project id and project now available on version

We've added a new trigger in this release to allow you to setup automation rules, that notify you when you are about to breach your service limits. For more details see our documentation.

AUT-1001 - Transition issue can leave issue in a bad state.

We fixed a number of small bugs in this release around rule execution errors and some smaller issues in the UI.

• AUT-997
• AUT-995
• AUT-996

We fixed a number of smaller bugs in this release and renamed the 'Refresh' issue action to 'Re-fetch' issue action to indicate that it only re-fetches issue data, and doesn't refresh the issue in a user's browser.

• AUT-992
• AUT-989
• AUT-755
• AUT-986

This release contains a fairly large change in the way we handle rules internally. Our aim was to make it more stable and efficient in terms of memory usage. The exact impact this will have comes down to your instance and specific Jira usage profile.

Other bugs fixed in this release:

• AUT-978 - Fixing bug where issues on transitions could have stale field values

#1 Feature request!! Ability to copy attachments and links.

Specifying "issue" at the front of smart values is now optional.{{issue.status.name}} is the same as {{status.name}}

We've fixed some bugs with scheduled rules not picking up issues that have changed since the last rule execution correctly. We also fixed delete attachment triggers that were using the 'should not match' option.

• AUT-977
• AUT-976

This release contains no functional changes. It simply provides better debug logs to help with tricky server support cases.

We introduced a critical bug in 3.12.11 that stopped event based rules from running under certain conditions. This release fixes that bug.

* Fixes bug where conditions cannot be added to branches (Pro only)

* Adds the ability to search for agile boards in sprint components (Pro only)

Bug fix for possible errors on add-on initialisation

Bug fix for Scheduled/Webhook triggers with extra execution for non existing issue.

Also included:

• AUT-960 - Better loop detection
• AUT-831- IE11 fixes
• AUT-934 - On manual trigger, group picker only displays first 20 groups

Bugfixes for MySQL and else-if

• AUT-956
• AUT-954

There is a new component called if/else under conditions (Pro only). It will allow you to perform actions if previous conditions fail.

Minor bugfix around setting users with mismatching name and keys

• AUT-925
• AUT-937

Minor bug fix release

• AUT-936

Bug fixes

• SLA selection in SLA threshold trigger
• Manual triggers fail in issues panel

You can now configure audit log entries to expire in the 'Global configuration' admin section of Automation for Jira!

You can choose how long you want to keep audit log entries for and when expiry should execute.

A word of caution for very large instances: This can put significant load on your database, so please schedule expiry out of hours. For more details on this see our blog!

• AUT-333

New easy to use smart-value list syntax

• New field to copy text field values from other issues and fields.
• AUT-924 - New smart-value syntax when dealing with lists
• AUT-920 - ability to specify locale when using date smart-values

Bug fix release containing:

• AUT-914 - Edge case - Transition Trigger firing incorrectly on Edit issue

We've fixed some bugs around deleted transitions and transition names containing accented or umlaut characters. Rules with a lot of JQL conditions should now also publish much faster!

• AUT-910
• AUT-909
• AUT-907

Bug fix around script field being unavailable

• AUT-875

Minor bug fixes

• AUT-899
• AUT-892
• AUT-870
• AUT-893

This release fixes an upgrade problem when upgrading from a really old (Atlassian Labs) version of Automation for Jira. We've also fixed an issue with link types not being filtered correctly for the 'Issue linked' trigger.

• AUT-895
• AUT-866

There was a serious bug that prevented Oracle creating an index on a column. Other bugs around Issue created when run synchronously with sub-tasks and also branching on recently created issues. This is a recommended upgrade.

• Oracle threw error when adding a unique index on a column.
• AUT-890 - Duplicate execution of "recently created" branches when run from a schedule
• AUT-876 - Some apis expect user key, others expect name.
• AUT-863 - When Issue created triggers process sub-tasks synchronously, they never complete

Bug fixes including fields missing during a transition, version startDate and releaseDate not being available, and added an ability for JQL and Webhook triggers to run without any issues being passed.

• AUT-881
• AUT-776
• AUT-804
• AUT-884
• AUT-883
• AUT-882
• AUT-700

• https://codebarrel.atlassian.net/browse/CAVE-1113
• https://codebarrel.atlassian.net/browse/AUT-881
• https://codebarrel.atlassian.net/browse/AUT-776
• https://codebarrel.atlassian.net/browse/AUT-804
• https://codebarrel.atlassian.net/browse/CAVE-1104
• https://codebarrel.atlassian.net/browse/AUT-884
• https://codebarrel.atlassian.net/browse/AUT-883
• https://codebarrel.atlassian.net/browse/AUT-882
• https://codebarrel.atlassian.net/browse/CAVE-1107
• https://codebarrel.atlassian.net/browse/AUT-700

Minor bug fix. Hiding away the version related actions for JSD only instances

* Adds release version action (pro only)

* Fixing bug with deleting global rules and rules with labels (pro only)

New in this release - large rule lists can now be grouped with the help of labels. If you have a lot of rules defined, you can now organise them into common themes for quick and easy access. See our release blog and documentation for more info! This is a Pro feature only.

We've also shipped a number of other improvements and bugfixes in this release:

• The SLA threshold breached trigger now supports more time ranges for limtis
• Helper functions to URL encode text in in smart-values and provide an issue's url
• Ability to select link type for related linked issues
• Fixes for the 'Add customer' action in how it looks up users by e-mail

Enjoy!

Fixed race condition for round-robin assigning of issues

Bug fixes for issues not being loaded correctly

Brand new triggers for software! You can now trigger rules on version released events, various sprint events as well as looping through the issues on versions & sprints. (Pro only)

• https://codebarrel.atlassian.net/browse/AUT-842
• https://codebarrel.atlassian.net/browse/AUT-845
• https://codebarrel.atlassian.net/browse/AUT-828
• https://codebarrel.atlassian.net/browse/CAVE-1003
• https://codebarrel.atlassian.net/browse/AUT-848
• https://codebarrel.atlassian.net/browse/AUT-804
• https://codebarrel.atlassian.net/browse/CAVE-1004

We've fixed two gnarly little bugs in this release:

• One broke the add-on during upgrade when certain data was present (AUT-851)
• The other caused problems with text input in the JQL condition field (AUT-827)

This release includes a few critical bugfixes:

• The admin UI works again in IE11
• Javascript error in the UI when navigating away while adding new components
• Advanced field improvements

Enjoy!

In this release we've revamped the 'Getting started' page to bring you our new sample rules.

This will make it easier for new users to get started with some example rules that we generate for a lot of common use cases for empty projects! See our release blog!

We've also optimised the audit log performance for the global audit log.

This release should result in a performance improvement during issue event serialisation in busy server instances. We are no longer serialising the Rank field (which in some circumstances would result in DB writes - AUT-794).

We also fixed a bug in the create issue action when switching from sub-tasks to normal issue types (causing the parent field to be incorrectly present and populated during rule execution).

We fixed a couple of bugs in this release:

• A number of multi-project scope related issues
• A bug with the user condition and multi-select user fields
• An issue with the move issue trigger configured with 'any' target project

Enjoy!

This release ships a new feature to allow you to restrict rules to run in certain projects only (see AUT-185 for details). Previously rules could only have a global or single project scope. With this release you can now select any number of projects for a rule to execute in! For more details see our release blog.

(please not that this feature is available in the 'pro' edition of Automation for Jira only)

We've also fixed a number of bugs:

• Multiple drag and drop related bugs
• SLA details can now be accessed via smart-values (AUT-786)
• Is customer user condition fix with missing participants field (AUT-777)

Bug fixes for the action picker not working for some situations

• https://codebarrel.atlassian.net/browse/AUT-775

Bug fixes include:

• Stride action failing with empty message body when there is a body.
• Adding ability to escape of smart values for use in webhooks
• Linking from branch components in audit log

This release fixes a bug we introduced in 3.9.2 & 3.9.3 that broke a number of custom field related components. Sorry folks!

• Switch to gitbook for our docs

From 3.9.2 (New version created trigger and bug fixes):

This release includes our new version created trigger, so you can run rules when a new version is created in a project!

We've also fixed a number of bugs:

• Better validation for URLs for team chat actions (Stride, Hipchat, Slack, Twilio)
• Updated our docs links to point to our new documenation at http://docs.codebarrel.io/automation/
• Removed the 'Copy rule' link if a user doesn't have permissions to create rules
• Creating a ServiceDesk customer works again even if there's no issues in the context

Enjoy!

This release includes our new version created trigger, so you can run rules when a new version is created in a project!

We've also fixed a number of bugs:

• Better validation for URLs for team chat actions (Stride, Hipchat, Slack, Twilio)
• Updated our docs links to point to our new documenation at http://docs.codebarrel.io/automation/
• Removed the 'Copy rule' link if a user doesn't have permissions to create rules
• Creating a ServiceDesk customer works again even if there's no issues in the context

Enjoy!

This release adds a new Stride integration to allow you to send messages to Atlassian Stride for those customers using it on the early access programme.

For full details, please visit our release blog!

This release fixes a timing dependant bug affecting Jira DataCenter only, where it was possible for Automation rules to execute on a node, before the search indexes for that node had been updated to the latest state (causing search based components like JQL conditions to fail incorrectly). For more details see https://codebarrel.atlassian.net/browse/AUT-727.

We've also fixed some minor UI glitches around loading spinners!

This release includes a bugfix for the issue deleted trigger (AUT-720). It also includes a small performance optimisation for rules where the rule actor doesn't have browse permission for the issue.

In our previous release we broke some smart-values for service desk related fields (specifically Organizations & SLAs). Now {{issue.Organizations.first.name}} works again!

Time for some internal cleanup just before Christmas! In this release we did a major internal re-factor to allow us to continue shipping features and improvements in the new year at the same pace you're used to from our team!

We also fixed some bugs in this release:

• When copying rules, rule details can be edited again
• Some sorting fixes in the new rule list table
• Minor improvements to the 'Issue moved' trigger

We fixed two bugs in this release:

• Timetracking values could be wrong when copying the field, if Jira's timetracking was configured with hour per day values with fractions (e.g. 7.6 hours per day)
• The user condition now correctly displays the summary in the sidebar when service desk options are configured (e.g. "user is a customer")

This release contains a ton of bug fixes and little improvements:

• Cascading select fields can now be set to 'None' using the More options JSON in Edit issue - AUT-662
• Issue security levels are now copied again when cloning issues - AUT-652
• The field value changed trigger no longer triggers incorrectly for attachments on create issue (when there's no attachments) - AUT-506
• Newsletter signup stops popping up when navigating back to the rule list - AUT-641
• Editing sprints with invalid values produces nicer errors now - AUT-659

Enjoy!

• https://codebarrel.atlassian.net/browse/AUT-656

This release contains a fix to make the 'Issue commented' trigger work again.

• Critical bug fix for those upgrading from the old Labs add-on

This is not needed for those who have are already on Automation for Jira - modern version.

We've fixed an annoying little bug where time tracking fields could not be copied with smart-values depending on the default or user locale set in the Jira instance.

The comment action now also displays an option to add comments multiple times in a more prominent spot!

This release fixes 2 bugs:

• SLA triggers were broken in a recent release.
• Anonymous comments would cause an exception for 'Issue commented' triggers

We've added a new dialog to allow your admins to signup to our newsletter and view latest blogs directly from within Automation for Jira. If you want to stay up-to-date on latest features and tips you can also sign-up for our newsletter on our website!

This release also includes significant performance improvements to reduce queries on the audit item tables. Instead we now query much smaller rule statistics tables to reduce load on your Jira database. In our testing this resulted in ~20% performance improvements when executing rules.

Finally we've also add the ability to perform partial regex matches in our compare condition to check if a bit of text *contains* a regular expression match.

We've fixed 2 little bugs in this release:

• When creating a sub-task, the 'Issue linked' trigger no longer kicks off a rule now
• Creating issues now skips screen checks for most fields.

Fixed an issue where smart field values weren't being correctly set & improvements to error handling on the rule creation flow.

Bug Fixes including:

• Removing email prefix only introduced in Jira 7.2
• Setting entity properties through create/edit did not work.
• businessDaysBetween did not work with Date (no time) fields
• Upping Jira's minimum version to 7.1

Professional translations for:

• Spanish
• Portuguese
• Japanese

Improved translations for:

• French
• German

Improved flow for creating new rules

Date function to calculate business days between 2 dates

Performance improvements

Remove subject prefix in outgoing emails

Bug Fixes

• Added smart field functions for strings
• Performance improvements

This release now includes a much improved German translation professionally reviewed by https://e2f.com/. Sehr gut!

We've also included 2 small bug fixes:

• Sending e-mails to the issue assignee now works again in all mail servers
• Workflow names with special characters in their name now also work again when selecting transitions on the 'Transition issue' action

You can now select a new option when editing the 'Organization' field in service desk projects to "Extract from reporter's e-mail address". This will set the organisation based on the reporter's e-mail domain.

This release also includes our first draft of French translations! We'll refine these in coming weeks with your (and our partner's) feedback!

We've also fixed a ton of niggles in this release:

• AUT-567 - Copying multi-group picker fields now works again
• AUTO-943 - Clearing the organization field is fixed
• AUT-478 - Better curl example in incoming webhooks with correct urls (if you are using Pro)
• AUT-574 - E-mails can now be sent to request participants
• AUT-571 - Fixed a caching bug with manual trigger rules in Jira Data Center (if you are using Pro)

If you'd like to take advantage of more Service Desk features in Automation for Jira please consider upgrading to our paid Pro offering.

We've released a ton of new features: Better management of SLAs in Jira Service Desk!

We've included a number of smaller improvements:

• Actions using http requests now will respect Jira's http proxy settings and SSL trust stores
• Editing request participants will now filter out the issue's reporter to avoid an error from Jira Service Desk
• Scheduling of rules has been made even more robust to avoid accidentally scheduling a rule twice if Jira's scheduler is running behind.

Enjoy!

We've further improved performance for large server instances in this release!

Some key changes in this release:

• There's now a single background thread that claims items from the database queue for processing (previously all executor threads would try to claim, leading to a lot of contention on this one database table)
• This single claimer thread then distributes tasks evenly to multiple rule executor threads (2 by default) for processing as soon as they become available. This guarantees far better utilisation of the execution thread pool. (currently the executor thread pool was often under-utilised leading to almost single threaded performance).

In summary, this release will be able to work through large backlogs in the automation queue faster, but at the same time produce less load for the database.

This release fixes AUT-552, a bug that for some customers caused no rules to execute due to database character encoding issues.

This includes more performance fixes for busy server instances.

We've optimised a lot of database queries and added indexes to the "AO_589059_AUTOMATION_QUEUE" table.

For more details see AUT-542.

Fixed an issue where Incoming Webhook Triggers would run JQL as an anonymous user.

• https://codebarrel.atlassian.net/browse/AUT-547

This release includes a new and improved 'To' field for the send e-mail action to make it easier to select user custom fields, as well as enter e-mail addresses and smart-values (AUT-262)!

We've also hugely improved performance for busy server instances (AUT-542):

• Collecting statistics from the automation_queue table now performs *much* faster if there's a backlog of items
• automation_queue payloads are now being zipped, therefore reducing database disk & network IO requirements.

Finally we also fixed a bug, where rules failed to export (AUT-541) and failed to copy versions correctly (AUT-543).

Certain smart-values would not work correctly with the set entity property action. That's now been fixed!

We've also improved the our math functions to handle large numbers better.

This release now has a new option to link to the most recently created issue in an automation rule using the 'Link issues' action. This is useful when you create a new issue automatically and want to immediately link it to the issue that triggered the rule.

We've also improved performance for busy server instance for event based rules.

Who would have thought that correctly detecting if an issue has been transitioned could be so hard! Well, turns out it is, thanks to Jira's sub-optimal event system.

This release fixes one final bug which stopped rules from triggering correctly on issue transitioned, when the change history provided by Jira's event could not be retrieved from the database yet at the time of rule execution (because Jira sometimes hadn't finished writing it yet).

This fixes a bug where scheduled rules could no longer be executed manually.

We also improved the issue transitioned trigger to run rules more reliably when weird timing issues prevent the changelog from being read.

We're shipping a few little improvements in this release:

• The from address for error notifications will now default to the default from address set in mail server settings in Jira Server
• Smart values now allow querying of a version release date. E.g. {{issue.fixVersions.first.releaseDate}}
• Finally we fixed a bug with the {{comment.internal}} flag for comments added via transition screens.

This release fixes a performance bug, that could cause excessive load for a busy server instance with many automation rules.

We now cache the automation rules when looking up manual triggers to display on the view issue page. This means when users visit the view issue page, there'll be far less database queries to lookup matching automation rules!

With this release, we added a small improvement that allows you to check if a field doesn't contain a particular value.

This release provides slightly better performance for issues with large change histories and event based rules.

Minor UI bug fixes.

This release fixes two issues:

• The related issues condition would exclude the trigger issue when using JQL to gather related issues. This could lead to some unexpected results. Fixed! (AUT-499)
• The Satisfaction field wasn't available for selection in the Field Value Changed trigger in server. (AUT-496)

This release fixes a rare problem, where the upgrade task from the old "Jira Automation" Atlassian Labs version could fail if some database tables are missing.

We've fixed a gnarly bug in this release, where in some circumstances, an automation rule would retrieve stale issue field values (instead of the latest issue field value).

• https://codebarrel.atlassian.net/browse/AUT-490

When there are less than 10 issues in a branch they are queued with the highest priority. This will for complete rules to run quicker.

We've fixed a few niggles in this release:

• Issue assigned & commented triggers now trigger regardles of how the issue is assigned or commented. So wether you're changing the assignee when editing an issue, or using the assign issue operation in Jira doesn't matter anymore - the rule will now trigger regardless!
• Sprint details now include startDate, endDate & completeDate. So you can access {{issue.Sprint.first.startDate}} for example
• We've also included some small performance improvements in the scheduler - it now adds items to the rule execution queue in bulk!

Cheers!

Time for some performance and stability improvements for the new database backed queue! We've fixed a hole number of things in this release:

• When an automation rule is disabled, deleted or edited, and executions currently in progress will be aborted immediately
• Massive performance improvement for retrieving individual audit log item details
• More correct way of checking if a scheduled rule is already in progress to prevent concurrent executions
• Better performance when claiming single items from the queue
• Finally we switched to optimistic locking when claiming items from the queue, which removes the need to create database row locks (which in rare circumstances could lead to catastrophic failures - AUT-487)

This is a recommended upgrade for anyone currently running 3.4.0 & 3.4.1. Enjoy!

• The user condition now provides a check to see if a user is or isn't a Service Desk customer
• You can now also edit Service Desk request participants using a simple multi select with the 'Edit issue' action
• The 'Manage watchers' action can now remove all watchers
• We've improved some German translations - Sehr gut!
• Finally we also fixed a rare bug that could lead to scheduled rules executing multiple times in certain high load Jira Data Center scenarios (AUT-483)