style | padding: 0 0.5em 0.5em 0.5em |
---|
style | margin: 0 1em 0.8em 0 |
---|
Div | ||
---|---|---|
| ||
Highlights (Core)
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Use the Send SQS Message action to relay event data |
You can now use the Send SQS Message action to relay event data from Bamboo notifications, Jira workflow transitions, and Jira Service Desk automation rule executions via the Amazon Simple Queue Service (SQS) |
for use in subsequent automation workflows. This allows you to decouple the capturing of event data from Jira Service Desk request approvals, Jira issue edits or Bamboo plan executions from the processing by other services |
: |
|
Highlights (Jira)
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Automate your workflows in Jira 8 and Jira Service Desk 4Most of the time we are able to retain Atlassian host product compatibility across major versions ('platform' versions in Atlassian lingo), but sometimes there are breaking changes that prevent that. While the Automate with AWS post function continued to work just fine in Jira 8, the Jira Service Desk 4 SPI changes required us to adjust the Automate with AWS then action in a backwards incompatible way. This release addresses the problem by providing separate artifacts for Jira 7.x and Jira 8.x compatibility.
|
|
Resolved issues
Release 1.5.0
2019-02-26
This release addresses the following issues:
Core
Stories
AAWS-330 – As a user, I want to send an SQS message so that I can enqueue jobs
Bamboo
Tasks
AAWS-530 – Drop support for Bamboo 5.14
AAWS-548 – Drop support for Bamboo 5.15
Jira
Technical debt
AAWS-492 – Address removal of com.atlassian.fugue in Jira Service Desk 4.0
Tasks
AAWS-532 – Drop support for Jira 7.3