-
Suggestion
-
Resolution: Duplicate
-
None
-
None
Hi,
Creating this for an add-on developer:
JIRA Cloud has the right idea; we can say goodbye to blowing up mailboxes with JIRA emails. The problem is that it's currently impossible to only receive messages I care about, making the integration far less useful than it could be.
So what do I want?
I want to receive Slack messages for events which I care about, namely events on issues I'm watching and @mentions in issues I'm not watching. I also want to control whether all of those messages cause Slack notifications, or just @mentions.
Right now, @jirabot can't be configured to only send messages for events I care about. If I connect @jirabot using direct messages, for example, I get a notification for EVERY event in a project. Yes, I can customize @jirabot to only send certain types of issues, but the type of issue has no bearing on whether I'm watching it. That's a non-starter.
Instead of DM, I can create a Slack channel that receives all JIRA messages to avoid the flood of notifications, but that has the opposite problem. Nothing's ever a notification, even if I care about it, so events on the issues I watch never get noticed.
I think the right solution here is to be able to configure JIRA Cloud to send me only messages that affect me from the get-go, instead of making Slack trying to figure out what to notify on and what not to notify on.
Side note. One stop-gap solution I tried which didn't work was to send all JIRA messages to a single Slack channel, and try to get Slack to create notifications whenever my name appears using Slack highlight words. But this didn't work, even for explicit @mentions in JIRA issues. According to an email I got from Slack,
One thing to note: this highlight word limitation [not notifying] is for bot messages which originate from an incoming webhook. Slack does recognize highlight words from a Bot User. I'm not sure if you will be able to take advantage of Bot Users in your specific case, but it might be worth exploring. Here's some documentation about Bot Users (https://api.slack.com/bot-users) and you can add one to your team here: https://my.slack.com/apps/A0F7YS25R-bots.
Even though JIRA Cloud is a bot user, highlight words didn't trigger notifications. At any rate, this would have only been a stop-gap solution, since a highlight word (my name) wouldn't necessarily show up in every message for every issue I'm watching. The right solution is to configure @jirabot.
- duplicates
-
- Closed
-
- Closed
- is depended on by
-
DEVHELP-587 Failed to load
- relates to
-
JST-447869 You do not have permission to view this issue
[API-127] Configure @jirabot to only send messages relevant to me
I hope there's a way to transfer votes to duplicates in JIRA. This ticket predates the other ticket by two years and has about half the votes.
Also, "Gathering Interest"? For 8 months? The integration has been effectively unusable for almost 3 years. This is the kind of complacency that turns people off Atlassian.
Please follow/vote for https://jira.atlassian.com/browse/API-80 we are actively tracking this feature request there. Thank you
I don't know when they implemented (recently, until 10/may it wasn't), but there is an option "For issues that match this filter -> Switch to JQL" in plugin's configuration page. I'm using this and it resolved for me 
Filtering is absolutely necessary. Everyone is being forced to move from HipChat to Slack and while Slack is a better product overall, the shotgun-style approach to notifications is, unfortunately, effectively worthless for us (and probably most everyone else, too). It just adds noise to Slack and people ignore the linked channels... entirely defeating the purpose.
When I say filter, I mean exactly what the OP suggests, filtering by user, and anything else, really. HipChat integration actually has (had?) this feature. You could setup filtering using any JQL you like (assignee=john.tolle or watcher=john.toll) for ultimate filtering flexibility. The only thing you couldn't grab with the HipChat integration was notification on things like @mentions which would need to be addressed separately somehow (otherwise they're pointless, too).
Right now, we're experimenting using our Jira Cloud instance with Slack's own Jira Server Alerts app since it uses Jira webhooks to capture data (and that allows JQL filtering)... but it is failing to send notifications on comments, so it's not quite there, either (although this might not be an issue with Jira Server, so YMMV.)
Hey emerson.farrugia,
I'm the product manager for the slack integrations here at Atlassian. Apologies for the lack of updates and transparency around this particular feature request.
I can assure you that this feature is top of mind for all of us on the team, and one of the things we're planning on picking up for active development very soon. One of the tasks for us to get this kicked off was to do some grooming of our tickets here, and that's why Sean marked this one as "Done", to reduce duplicates and consolidate the ticket into one feature request. While we can't transfer the votes, I know that these two tickets (this one and the one linked) represent the vast majority of votes for feature requests for our integration, and I promise that significance won't be missing in how we evaluate feature requests
I'd like to learn more about how you're using the integration, what you're hoping for from it, etc. Please email me at trevor.thompson@atlassian.com
(I encourage anyone reading this to do so) and we'll set up some time to chat about how we can better help you.
Thanks for your patience! Updates on this soon!!
Trevor Thompson
Product Manager, Product Integrations