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.
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.
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)
We broke the lite version in our last release - sorry. Here comes the fix!
Minor bug fixes.
Issues fixed in this release:
Jira 8.8 support and several bug fixes and a few new features.
Issues fixed in this release:
Issues fixed in this release:
Implemented month time range for performance insights.
Issues fixed in this release:
Issues fixed in this release:
Issues fixed in this release:
Issues fixed in this release:
Issues fixed in this release:
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:
Issues fixed in this release:
Issues fixed in this release:
Issues fixed in this release:
Issues fixed in this release:
Issues fixed in this release:
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:
Issues fixed in this release:
Issues fixed in this release:
Issues fixed in this release:
Issues fixed in this release:
New performance insights for rule statistics feature added to the "â¦" menu in both global and project admin.
Various improvements and fixes in this release:
Fixes a bug in assignee picker field (cloud only)
Issues fixed in this release:
Issues fixed in this release:
Issues fixed in this release:
Issues fixed in this release:
Issues fixed in this release:
Issues fixed in this release:
Issues fixed in this release:
Issues fixed in this release:
Issues fixed in this release:
Issues fixed in this release:
Issues fixed in this release:
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:
Issues fixed in this release:
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:
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:
Issues fixed in this release:
Issues fixed in this release:
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:
Added multi select field and checkbox support for issue condition field.
Issues included in this release:
Issues fixed in this release:
Issues fixed in this release:
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.
Various bug fixes
Minor improvement to add hovers for truncated multi-select values
Bug fix around smart values support for JQL trigger
This release contains a minor API compatibility fix.
Minor bug fixes
No issue keys found since last release. Please update these release notes!New feature: Access outgoing webhook response data in your rules
Fixed some UI related bugs
Fix for edit comment event picked up by 'Issue commented' rules
Added support for copying and editing Tempo accounts in the Create/Edit/Transition actions
Minor performance improvement for instances with lots of users
AUT-1353 - Tenant Info shouldn't retrieve user count in server
Jira 8.0.1 introduced some API breakages that weren't present in Jira 8.0.0. This release fixes this compatibility problem.
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).
We've fixed a few gnarly bugs around publishing custom events and rules triggered by field changes to the assignee field.
We've added support to edit original and remaining estimate fields on issues now. This release also includes a number of bug fixes:
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).
Fixed bug with entity properties API breakage in Jira 7.x
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!
Bug fix for Server Schedules
Small bug fix
Fix for bug affecting user entity properties in smart-values
Bug fix for failing Microsoft Teams notifications
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.
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
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.
Fixes bug with starting a trial in lite
zBug fix for manage waters
We've fixed a few minor bugs in this release and include some internal engine room fixes to enable future work.
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.
Bugfix
We've fixed a translation bug with the Epic Link field, and some UI glitches with long text in the sidebar.
Fixing a bug around global configuration 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:
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.
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).
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:
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:
Trying to fix version incompatibility issues of previous deploy
No issue keys found since last release. Please update these release notes!Fix where the rule editor could result in a javascript error in rare cases
This release fixes a deadlock that can happen with MySQL under high load scenarios.
No issue keys found since last release. Please update these release notes!We've fixed a few bugs that could result in navigation problems when clicking certain links.
Added support for browser navigation and lots of bug fixes, including a scheduling bug that could stop scheduled/polling rules running.
JIRA 7.12 support
We've updated some product logos to the latest in this release.
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!
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:
Enjoy!
We're bringing back Jira Data Center support in this release.
Bug fixes for Insight fields and picking Epics
Bug fixes for service desk, webhooks and other various fixes.
Bug fix for handling masked email addresses
In this release we've updated all our user pickers to fix a number of different bugs.
We've fixed a bug in this release that broke sorting by different columns in the rule list.
Jira 7.11 support
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.
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.
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:
#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.
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:
There is a new component called if/else under conditions (Pro only). It will allow you to perform actions if previous conditions fail.
Minor bug fix release
Bug fixes
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!
New easy to use smart-value list syntax
Bug fix release containing:
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!
Bug fix around script field being unavailable
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.
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.
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.
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:
Enjoy!
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)
We've fixed two gnarly little bugs in this release:
This release includes a few critical bugfixes:
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:
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:
Bug fixes for the action picker not working for some situations
Bug fixes include:
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!
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:
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:
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:
We fixed two bugs in this release:
This release contains a ton of bug fixes and little improvements:
Enjoy!
This release contains a fix to make the 'Issue commented' trigger work again.
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:
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:
Fixed an issue where smart field values weren't being correctly set & improvements to error handling on the rule creation flow.
Bug Fixes including:
Professional translations for:
Improved translations for:
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
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:
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:
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:
Enjoy!
We've further improved performance for large server instances in this release!
Some key changes in this release:
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.
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):
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:
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.