How to configure Slack notifications for issues moved between projects
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Atlassian Slack Integration for Jira only supports a limited number of events that can be used as a trigger for notifications: "Issue created", "Assignee updated", "Issue commented" and "Issue transitioned". However, very often issues are being moved between projects, and for such scenario there is no event in the Slack integration that could be used to configure notifications for.
Solution
There is a known feature request available to add "Issue moved" event to the official Slack integration plugin: API-182 - Enable "issue moved" notification on slack
If Automation for Jira is available in the same environment, the following workaround can be used to receive notifications for such events:
Create a new automation rule in Automation for Jira.
Set event for the rule to "Issue moved", and specify projects as needed.
Set action for the rule to "Publish event" → Issue Created.
Make sure you have enabled the option "Publish newer style 'IssueEventBundle'".
Save and turn on the rule.
Please note that the rule will raise "Issue created" event every time it is executed, so if you have any global listeners for this type of event, they will be executed. This is exactly what makes Slack integration being able to recognize such events and send notifications to configured channels.
Was this helpful?