-
Suggestion
-
Resolution: Unresolved
-
None
-
None
Problem Definition
Currently, Slack trigger notifications for Issue Created, Assignee Updated, Comments and Issue transitions. There is no option to trigger a notification when an issue is moved from a project to another.
Suggested Solution
Implement an additional option to trigger notifications for moved issues.
Why this is important
Some customers want to keep track of issues that are being moved from one project to another by just looking to the notification on Slack instead of checking issue history.
Workaround
Using Automation for Jira 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.
- has a derivative of
-
- Gathering Interest
- is cloned from
-
- Gathering Interest
[API-182] Enable "issue moved" notification on slack
| Description |
Original:
h3. Problem Definition
Currently, Slack trigger notifications for Issue Created, Assignee Updated, Comments and Issue transitions. There is no option to trigger a notification when an issue is moved from a project to another. h3. Suggested Solution Implement an additional option to trigger notifications for moved issues. h3. Why this is important Some customers want to keep track of issues that are being moved from one project to another by just looking to the notification on Slack instead of checking issue history. h3. Workaround Using Automation for Jira 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. |
New:
h3. Problem Definition
Currently, Slack trigger notifications for Issue Created, Assignee Updated, Comments and Issue transitions. There is no option to trigger a notification when an issue is moved from a project to another. h3. Suggested Solution Implement an additional option to trigger notifications for moved issues. h3. Why this is important Some customers want to keep track of issues that are being moved from one project to another by just looking to the notification on Slack instead of checking issue history. h3. Workaround Using Automation for Jira 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. |
| Description |
Original:
h3. Problem Definition
Currently, Slack trigger notifications for Issue Created, Assignee Updated, Comments and Issue transitions. There is no option to trigger a notification when an issue is moved from a project to another. h3. Suggested Solution Implement an additional option to trigger notifications for moved issues. h3. Why this is important Some customers want to keep track of issues that are being moved from one project to another by just looking to the notification on Slack instead of checking issue history. h3. Workaround NA |
New:
h3. Problem Definition
Currently, Slack trigger notifications for Issue Created, Assignee Updated, Comments and Issue transitions. There is no option to trigger a notification when an issue is moved from a project to another. h3. Suggested Solution Implement an additional option to trigger notifications for moved issues. h3. Why this is important Some customers want to keep track of issues that are being moved from one project to another by just looking to the notification on Slack instead of checking issue history. h3. Workaround Using Automation for Jira 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. |
This is working for me. Go to Project settings --> Automation ---> New rule ---> type in Issue Moved
Then select your source project and target project. click save. Select Then: Add an action and search for Send slack message. You need to create a slack webhook url and customize your slack message in the description. Select your channel to send the message and save it. Publish the automation.
We have Jira cloud though
Why is this issue still active? Why not close this and gather information on API-20 that already has 78 votes and been around since 2019. It gets tiring running into a missing Jira piece that has been languishing for years yet we get new behavior that few of us want.
| Link | New: This issue has a derivative of JSWSERVER-20268 [ JSWSERVER-20268 ] |
| Link | Original: This issue was cloned as JSWSERVER-20268 [ JSWSERVER-20268 ] |
There is unfortunately no option for us to do that and we also have Jira cloud.