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
Release notes
Upgrading Automation for Jira
Release notes
Upgrading Automation for Jira
Release notes
Upgrading Automation for Jira
Release notes
Upgrading Automation for Jira
Release notes
Upgrading Automation for Jira
Release notes
Upgrading Automation for Jira
Release notes
Upgrading Automation for Jira
Release notes
Upgrading Automation for Jira
Release notes
Upgrading Automation for Jira
Release notes
Upgrading Automation for Jira
Release notes
Upgrading Automation for Jira
Release notes
Upgrading Automation for Jira
Release notes
Upgrading Automation for Jira
Release notes
Upgrading Automation for Jira
Release notes
Upgrading Automation for Jira
Release notes
Upgrading Automation for Jira
Release notes
Upgrading Automation for Jira
Release notes
Upgrading Automation for Jira
Release notes
Upgrading Automation for Jira
Release notes
Upgrading Automation for Jira
Release notes
Upgrading Automation for Jira
Release notes
Upgrading Automation for Jira
Release notes
Upgrading Automation for Jira
Release notes
Upgrading Automation for Jira
Release notes
Upgrading Automation for Jira
Release notes
Upgrading Automation for Jira
Release notes
Upgrading Automation for Jira
Release notes
Upgrading 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:
Issues fixed in this release:
Jira 8.8 support and several bug fixes and a few new features.
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:
Issues fixed in this release:
Implemented month time range for performance insights.
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:
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:
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:
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:
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:
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:
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)
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:
Issues fixed in this release:
Issues fixed in this release:
Issues fixed in this release:
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.
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.
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:
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:
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:
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!
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:
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:
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:
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:
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.
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
Various bug fixes
Minor improvement to add hovers for truncated multi-select values
Minor improvement to add hovers for truncated multi-select values
Bug fix around smart values support for JQL trigger
Bug fix around smart values support for JQL trigger
This release contains a minor API compatibility fix.
This release contains a minor API compatibility fix.
Minor bug fixes
No issue keys found since last release. Please update these release notes!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
New feature: Access outgoing webhook response data in your rules
Fixed some UI related bugs
Fixed some UI related bugs
Fix for edit comment event picked up by 'Issue commented' rules
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
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
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.
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 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 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 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).
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
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!
We've added Jira 8 compatibility in this release. We also introduced a new action to allow you to log work on Jira issues!
Bug fix for Server Schedules
Bug fix for Server Schedules
Small bug fix
Small bug fix
Fix for bug affecting user entity properties in smart-values
Fix for bug affecting user entity properties in smart-values
Bug fix for failing Microsoft Teams notifications
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.
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
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.
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
Fixes bug with starting a trial in lite
Bug fix for manage waters and setting Org based on reporters email address.
Bug fix for manage waters and setting Org based on reporters email address.
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 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.
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
Bugfix
We've fixed a translation bug with the Epic Link field, and some UI glitches with long text in the sidebar.
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
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 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.
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).
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).
This release fixes a small issue with our new licensing logic to allow server licenses again in Jira Data Center until the grandfathering end date of 3rd of September 2019.
This release fixes a small issue with our new licensing logic to allow server licenses again in Jira Data Center until the grandfathering end date of 3rd of September 2019.
After this date as of version 4.0.0, you will no longer be able to run Automation for Jira in Jira Data Center with a server license for Automation for Jira. You will have to upgrade to a Data Center subscription of Automation for Jira. If you are already using a Data Center license for Automation for Jira, you can safely ignore this notice.
As of version 4.0.0, you will no longer be able to run Automation for Jira in Jira Data Center with a server license for Automation for Jira. You will have to upgrade to a Data Center subscription of Automation for Jira. If you are already using a Data Center license for Automation for Jira, you can safely ignore this notice.
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!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
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!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.
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.
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
JIRA 7.12 & Data Center support
Also including bug fixes:
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!
This release adds support for the new Data Center requirements!
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!
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.
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 block" 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)* Fixes bug with deleting global rules and rules with labels
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!
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.
We've fixed two gnarly little bugs in this release:
This release includes a few critical bugfixes:
Enjoy!
You can now be off and running with Sprint triggers! Fire off your rules when a sprint is created, starts or completes.
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.
We've also fixed a number of bugs:
Bug fixes for the action picker not working in 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!
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:
Also fixes bug where components can be duplicated across branches.
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 more performance improvements and 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:
Enjoy!
This is a massive release. First up we added a new SLA trigger to notify you when a Jira Service Desk issue's SLA breaches, is about to breach or has already breached. For more details on all of the awesome Service Desk features in this release see our release blog: Better management of SLAs in Jira Service Desk!
This release also includes a new issue linked trigger, so you can run rules when an issue is linked!
Finally we've also 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.
Some small UI bug fixes.
This release fixes to issues:
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).
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:
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:
This is a recommended upgrade for anyone currently running 3.4.0 & 3.4.1. Enjoy!
Brand new in this release - a persisted automation rule execution queue! Never loose rule executions again due to Jira Server crashes or restarts.
All event and schedule based rule executions are now persisted to a database backed queue. Processing of this queue will resume on server restarts, so no events get lost ever again!
We've also improved performance in Jira Server as well as Jira Data Center. In Jira Server there's now more background threads to process the new queue and in Jira Data Center your cluster nodes will share the load of processing the queue across the entire cluster!
Manual executions and synchronous event based rules will still execute in memory as they did previously.
This is a great release with a cool new feature - the ability to evaluate math expressions. This allows you to work with numbers and create calculated customfields.
You can read about this in more detail in our blog - Calculated customfields and math expressions.
Also in this release:
We're shipping two small UI improvements in this release:
This release contains the latest German translations, as well as some bugfixes for the field value changed trigger when used with translated custom fields.
We also fixed some bugs in our onboarding flow in this release!
This release improves the 'Add watchers' action so you can now 'Manage watchers' and remove specific watchers from issues as well!
We've also fixed some performance issues with large issues (particularly those containing many comments and/or worklogs). They are now serialised on a background thread for asynchronous rules, and comments/worklogs are lazy loaded (AUT-449).
Finally we also fixed a bug where rules exceeding the search limit in Jira would stop executing instead of processing issues up to this limit (AUT-451).
This release contains a small work-around bug fix, to make Automation work in Jira instances that have a mis-configured base url (e.g. when using Jira behind a misconfigured reverse proxy that reports requests to Jira as 'http' instead of 'https').
This version includes some slight wording improvements in the new user condition UI.
This release includes an improved user condition allowing you to define multiple criteria to match users. For more details visit our release blog!
The previous 3.3.x releases (3.3.1 and 3.3.2) contained a critical bug (AUT-437) that stopped project scoped rules from being limited to executing in those projects only. Instead rules ignored the project scope and executed for events from all projects. This has now been fixed - we're really sorry if you were affected by this!
We've also fixed a smaller bug that prevented multiple event triggers from validating if they were configured with custom even types: AUT-438
If you previously upgraded to 3.3.1 or 3.3.2, then please upgrade to this version as soon as possible!
This release fixes a number of minor bugs. Namely:
Yep, that's right - we're bringing back synchronous issue event triggers in this release! You can now choose to execute rules instantly, when an issue event occurs again. See our release blog for full details.
We've also included a better fields picker everywhere you can edit fields. Enjoy!
This release contains a critical bugfix that could lead to SQL related exceptions when saving audit logs for automation rules using actions provided by third party extensions: AUT-424
These rules would end up stuck 'IN PROGRESS' for up to an hour.
This release contains updated German translations and a fix for a potential permission issue resulting in 'Actor does not have permission to view all issues in list' errors in the audit log in rare circumstance (https://codebarrel.atlassian.net/browse/AUT-423).
This release contains fixes for two issues:
This release contains a fix for AUT-418, which could lead to javascript errors when trying to access the Automation admin sections on Jira instances that are accessible via multiple URLs (e.g. http vs https).
Today we bring you some software love.
Enjoy!
Added support for the following fields in field actions:
Also numerous bug fixes including
Enjoy!
This release contains a number of little gems:
Enjoy!
This release includes a few small improvements and bug fixes:
Enjoy! Happy Monday!
We had a fairly serious bug, that would stop automation rules from working that used a deleted custom field in their simple forms (e.g. edit or transition action). Fixed - those rules will now run again and the config UI will also work correctly.
This version adds support to update the 'Epic Name' field in the simple form anywhere you can update fields (create, edit and transition issue).
This should make automatically creating Epics a lot easier now!
This release includes a fix for third party extensions for Automation for Jira, when processing multiple issues at a time (e.g. as produced by the scheduled trigger). These are now processed in a single batch again!
We've also made some small cosmetic improvements to the display of change items in the audit log.
It's happening! We've spent the past few weeks coding, testing and refining this upgrade, and we're now pleased to offer a version of Automation for Jira that upgrades the old 'Jira Automation' add-on.
If you are currently running both the old Atlassian Labs 'Jira Automation' add-on and Automation for Jira side by side then with this upgrade, all rules will be migrated across to Automation for Jira and the old add-on can be un-installed.
This release also adds full support for third party extensions (e.g. PDF Automation Plugin for Jira by Midori)
For more details see the 'Third party extension support' section in our combined release blog with the new 'Automation Lite for Jira server' release.
***Please read our upgrade guide if you are currently also using the old 'Jira Automation' Atlassian labs add-on***
We've added a few small improvements in this release:
Enjoy!
Some really minor things:
One of our most popular requests has been to add permissions around which project administrators can create rules. This release includes the ability for global administrators to disallow all project admins or use groups for finer grained control
This release adds a few improvements around error handling in Automation for Jira:
For full details see our release blog!
We've also fixed a small bug, when using smart-values with date pickers.
This release fixes a few minor bugs around parsing of smart-values. You can now also close smart-values for multi-values with {{/}}. For example: {{#issue.fields.labels}}{{.}},{{/}}
We've also shipped a few engineering improvements under the hood in preparation for the Automation Lite for Server upgrade that will be released in the coming weeks.
Features
Bug Fixes
Previously it wasn't possible to select sub-task issue types in the edit issue action. This has now been fixed and you can use the edit issue action to change sub-task issue types (or change parent issue types). Please note that converting from parent to sub-task isn't possible though (the audit log will contain an error).
We've also shipped a number of improvements behind the scenes to keep the codebase clean!
Enjoy!
This release includes a minor work-around for a bug affecting a small subset of Jira Service Desk customers.
Fixing bug for "createdIssues" and "Created Issues Branch" where only last created issue was being used instead all of them.
Fixed bugs:
This release fixes a minor bug that snuck in, where the due date wasn't being cloned to the new issue when using the 'Clone issue' action. Fixed!
Sometimes you want the latest version of the issue in the rule. E.g. after a transition or issue edit, you may want to reference the new fields in smart fields.
You can now add a "Refresh issue" action to your rule and all references to issue or trigger issue will be the latest issue.
This release includes updated German translation and a new option to transition issues for global administrators!
Any global admin can now pick a specific transition from any workflow that will be used to transition an issue. The old way of selecting a destination status and transition match still works too!
You can now access more fields on the user and project objects in smart values.
Also includes a bug fix for date fields including Due Date.
This release adds the ability to set the 'from' and 'reply-to' addresses for outgoing e-mails from the send e-mail action. Please visit our release blog for full details. Enjoy!
In this release we are easing the limits around the number of executions that can be executed in a given amount of time. You may have seen rules being "throttled" or disabled due to a possible "loop detection" - this should now be a rare event.
This release adds a few improvements to the audit log!
For more details please see our release blog!
Fixing bug that can cause related issues action not to find any issues. Happens when "Current issue" is selected and the first condition in the branch is a JQL condition. Internal optimisations caused this to fail.
Reopen Template would fail when used to create a new issue.
We've improved the related issues action to allow you to select the current issue. This can be useful if you need to perform different actions for the same issue depending on different values that may be set on a field. For example, you can add 2 related issue branches for the current issue and assign the issue to 2 different users with the help of a condition that checks for 2 different field values on those related branches!
We've also added an advanced new action to set entity properties, for issues, projects and users.
This release also contains a bug fix where values cleared from single select fields with the keyboard would cause an error when trying to save an Automation rule!
This version improves audit log messages when no issues can be found due to the "Only include issues that have changed since the last time this rule executed" checkbox being checked.
We've also fixed a rare bug where the audit log would not load.
This release contains a fix for AUT-248. In rare circumstances, issues created by an automation rule could not be transitioned. The underlying cause is a bug in Jira's events system, however this version contains a workaround for this bug.
This release fixes an annoying little bug that snuck in, in yesterday's release where the create issue form would always switch back to the first project & issue type when editing an existing action. Sorry about the inconvenience!
Enjoy!
Some great little features in this release.
You can now access the project category with smart values using: {{issue.fields.project.projectCategory.name}}
We've also improved the wording around the related issues action to distinguish between project centric and global rules in a more clear way and JQL related queries will no longer include the trigger issue!
Small bugfix release that fixes 2 issues:
The audit log will now show who edited an automation rule. You'll be able to see who:
For more details visit our release blog!
We've added a number of new field types to the simple forms in Automation for Jira with this release. You can now edit all of these fields without using the 'Advanced' JSON block:
We've also introduced some service limits to ensure Automation for Jira doesn't cause performance issues in your Jira instance.
For more details on these limits and the new fields read our release blog!
In this release we have added better support for SQL 2008 and have ensured all parts of Automation now work.
This release fixes a few minor bugs, namely:
We've greatly improved issue linking in this release. Gone is the need for the "Advanced" section in order to link issues. There's now a new "Link issues" action and you can also link issues, when editing, creating and transitioning issues with the simple form builder!
For full details please read our release blog. Enjoy!
Some small improvements!
First it's now possible to access the comment visibility in a condition using the {{comment.visibility}} smart-value. {{comment.visibility.type}} will return either 'group' or 'role' and {{comment.visibility.value}} will return the actual group or role the comment is visible for.
We've also made a small improvement to the edit issue action, allowing you to edit fields that are not on the edit issue screen!
We have totally revamped the Assign Issue action - https://blog.codebarrel.io/smart-assign-jira-issues-load-balancing-round-robin-and-more-530f3a48bb25#.mvjvpdplp
Some highlights for assigning:
Other inclusions:
Another webhook related release in the same day! This time it's a bugfix for outgoing webhooks. Previously, outgoing webhook bodies were not being UTF-8 encoded, which would lead to problems if issue data contained funky characters.
That's been fixed now and outgoing webhook bodies will now use the UTF-8 charset!
Incoming Webhooks are a great way to integrate with third party systems to kick off an automation rule in Jira. E.g. when a PR is created in BitBucket!
Up until now accessing extra data in smart-values required the webhook body to set a 'data' field. Other top level fields were ignored.
This is no longer the case! With this release any top level field can be accessed. That means you can do funky things like {{webhookData.pullrequest.source.branch.name.match("([A-Z]*-\d+)")}} when receiving a BitBucket PR created webhook to extract the issue key from the branch name using our new string functions!
Another week and we've squashed some more bugs!
Enjoy!
"AUTOMATION now with more String!"
Yep that's right - we've added some string manipulation functions to any string smart-value in Automation for Jira!
For a full list of available functions and examples, please see our docs on working with strings!
We also fixed a small bug where the field value changed trigger didn't work with the 'Components' field and shipped some small improvements to the comparator condition (you can now search for 'starts with' and 'contains').
This release fixes a small bug that broke copying of date custom fields in the 'Advanced' section of the edit issue action.
Visit AUT-156 for the full details!
This release adds much better support for creating sub-tasks when there's required fields. The simple 'Create sub-tasks' action now provides a helpful error with the option to switch to the full 'Create issue' action which will allow setting required field values.
Create issue now also makes it easy to set the parent issue if a sub-task type is selected! For full details see our release blog.
We also fixed a bug where a couple of translations went missing! Pardon!
This release fixes a bug where users with renamed usernames were causing an exception to be thrown in the add watchers action.
We've also made some small improvements to the audit log to ensure associated items wont contain duplicates and are sorted. Enjoy!
This release adds better support for date custom fields allowing you to perform date operations on any field (not just system fields):{{#issue.fields.Demo Date field}}func=minusDays(4){{/issue.fields.Demo Date field}}
See AUT-147 for full details!
We squashed two bugs in this release, one which was particularly gnarly!
In some circumstances, JQL conditions (and related issue conditions/actions) in server could fail due to timing issues. The problem was that the automation rule would kick off and run a JQL search before Jira had finished indexing the relevant issue (See AUT-143 for more details). Please upgrade soon to get this fix!
We've also fixed a minor bug with cron expressions including ranges in the day of week field: AUT-130
Time for some small improvements! This release adds better list support in smart-values. You can now access, the first and last members of any list (such as an issue's comments) and also get the total size and index. See smart lists for more details!
We also improved outgoing webhooks! You can now specify a custom POST body (or the issue JSON) with support for smart-values, to make it even easier to interact with third party APIs!
Finally 'send e-mail' now lets you specify if you're sending a HTML or plain text e-mail! See our release blog for full details - enjoy!
This release fixes a minor bug where the related issues condition would not restrict queries by project for project specific rules. This could mean the condition would pass even though there were no related issues in the current project (but in another project).
We've also re-factored some of the internals to handle certain error conditions better when performing actions on Jira. This will now provide more useful errors in the audit log!
There's a couple of little gems in this release that will make Automation for Jira even easier to use.
*Better Transitions*
A lot of users use Automation for Jira, to keep parent and sub-task (or Epic and story) statuses in sync. Up until now this required a new rule per status. No more - with this release, the transition action now supports smart-values and some special values like 'Copy from parent' or 'Copy from epic' to make this much simpler.
*Simpler scheduled triggers*
Previously we included two separate scheduled triggers in Automation for Jira: One to run a JQL search on a schedule and another to simply kick of a rule to for example create issues on a schedule.This was causing a lot of confusion though and customers were often configuring the non JQL scheduled trigger and wondering why this couldn't be used with a JQL condition.Now we've combined the two with a lot more guidance in the UI! Enjoy!
Yes - it has come to this point. It's a new year, you've come to work on Wednesday all well intentioned, you fix some bugs and :boom: - you've introduced a new bug with your 'fixes'!
Turns out the incoming webhook validation to avoid duplicate webhook URLs added in 1.1.6 released yesterday was a little overzealous and preventing all existing webhooks from being edited. This has now been fixed!
This fixes a few minor bugs:
Any global admin can now import and export automation rules! Multiple rules can be imported in one go, and exports from Server to Cloud and vice versa are also possible! Read our blog for more details.
We also added some categorisation and type ahead search for triggers and actions to make it easier to find just the right trigger or action for the job. Enjoy!
Our list of triggers and actions where getting quite large so now there's a typeahead search and categorisation that should make it easier to find just the trigger and action you need!
We also added a bit of extra debug logging in this release to help with tricky support cases. This will only show up if debug logging is enabled manually though by a global admin.
This release provides some better German translations! Huge shoutout to Stefan Haller from linkyard for spending some of his time correcting my terrible German! Dankeschön!
We also improved audit log errors when there's issues sending e-mails in this release.
This release adds global automation rules that can be configured by any global admin. This allows you to configure a single rule to automate issues in many different projects.
This release also slightly relaxes validation of Slack webhook URLs in server such that the integration can also be used with Mattermost.
This release adds global automation rules that can be configured by any global admin. This allows you to configure a single rule to automate issues in many different projects.
This release fixes a minor bug where copying automation rules from a different project was broken. Enjoy and happy new year!
This release fixes a small bug where certain CRON schedules could cause issues for the scheduler.
Happy new year (almost!). This release fixes 2 minor bugs:
This release contains a fix for a bug that can cause the Field Value Changed Trigger to not fire for customfields.
This release adds support for simple number custom fields anywhere you can edit fields (create, edit, transition actions...).
Sometimes you just want to transition an issue back to the same status (and set some fields). This version now also adds a new destination status "Same status (loop)" to the transition action to make this easy if you have a lot of status that support loop transitions. Enjoy!
It also contains a fix for a rare upgrade issue that could affect 1.0.17 and 1.0.18. Please upgrade to this version instead!
This release contains the following fixes
Contains the following fixes:
Bugs included in this release:
In this version we made editing and working with issues fields easier. We added:
The to number can now contain smart-values. This allows you to send to numbers that are defined in custom fields -
{{issue.fields.Customer Number}}
There was a bug when selecting a rule to copy - an "Unknown Error" dialog appeared. This now behaves as expected.
Fixed bug for related issues where Epic was specified.
Two new features before the week is over:
Check out the release blog for more details!
This release fixes AUT-65, a critical bug with MySQL where automation rules with related issues could not be edited or deleted.
Time to add some incremental improvements as well as some new features this week:
Read our release blog for full details!
Sadly it has come to this already and this release doesn't have any exciting new features. However we have squashed a few annoying bugs around validation of related issue actions and assignee pickers!
Fear not though - we've got plenty of exciting features in the pipeline still!
A huge number of new features for automating related issues:
See our release blog for full details!
Yes - that's right all the awesome automation features available in Cloud are now also available to install in Server with this initial release of Automation for Jira for Server.