Notification/Automation

[Michelle]

Hi All, I am trying to setup an automation to send to Slack from Jira.  Instead of receiving the email updates from Jira when an issue has been updated, we would like to see the updates for the issue in Slack.  I have made great strides, but still not getting what we want from the automation.  Below is where I am at with this request.  The request runs, but it brings back 100 records and only links to issues.  We only want to see when a Jira issue has been updated.  The same details we would see in the automated Jira email.  For example, the Jira issue key, the assignee who made the update, the last comment added to the issue, the date, time of the update, and the URL so that we can click on the URL of the issue to go directly into Jira from Slack.  Any guidance you can provide would be greatly appreciated.

[Bill Sheboy]

Hi @Michelle Lambert -- Welcome to the Atlassian Community!

The rule you show uses the Scheduled Trigger and a Lookup Issues action with what appears to be invalid JQL, and you note sending Slack messages "when a Jira issue has been updated."

First, if you indeed want to send the messages when the issue is updated, you will need several rules using different triggers rather than the Scheduled one.  These include at least:

• issue created
• issue updated
• issue transitioned
• issue linked
• issue commented
• ...

That would send the messages, one-by-one as issues are updated.  Is that what you wanted, or to instead send a periodic / scheduled summary (e.g., "all these issues changed today")?

Next, it is not possible to exactly match the email Jira sends for notifications.  The reason is some of the rule's access to changelog information will not show the same format (or details) which Jira notifications are getting from their custom-code.  An alternative (using the triggers mentioned above) is to send a message such as "Issue ABC-123 was updated" with a hyperlink to open the issue.

Finally, notifications are configurable both at a site and an individual user's level.  Would you see these messages going to a shared, Slack channel (which will likely become quite noisy), individual messages sent to specific people, or both?  Sending to a channel is easy; sending to an individual by-mention will require storing their Slack user ID values somewhere in Jira (such as with entity properties) to reference by user.

Kind regards,
Bill

[Michelle]

Bill,

Thank you for your feedback.  To answer your questions:

• Send the messages, one-by-one as issues are updated.
• What is the code to set this scenario up?  "send a message such as "Issue ABC-123 was updated" with a hyperlink to open the issue."
• The message from Jira to Slack would go to a private shared channel just for my team.

Any further assistance you can provide would be greatly appreciated.

Regards,
Michelle

[Scott Schellhardt]

Hi Michelle,

Welcome to the Atlassian Community! Can you provide some additional context to this request ? I have something similar running in my instance that may be able to get you headed in the right direction !

[Michelle]

Scott,

Thank you for the details.  I am not sure what other context to provide.  Basically, instead of receiving the automated Jira emails, my team wants to see the same information from the email in Slack.  I understand from Bill that I will not be able to get exactly what I see in email sent to Slack.  I will play around with what you shared and see if I can get this to work in my environment.

I noticed in your screen shot that you selected to check the "Sender" box.  What does it mean to "Send message as Automation user"?  I was using the Channel field to send the message over to Slack.  We have a private channel created just for this effort.  Only my team can access the channel.

Regards,
Michelle