Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to "mute" the jirabot notification in Slack.

Jitu
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 28, 2020

I have jirabot/Jira Cloud integration in Slack. I love the idea of stream of all the changes happening to tickets. But if say I have 10 tickets in flight then I get 10*4 -> 40 slack notifications distracting me throughout the day. (as the ticket moves through various QA stages etc.) ..QA started, Qa finished, read for merge, merge done ..released etc.. 

I want these notification but I want them muted so I only look at them when interested.

Slack allows a channel to be muted. I want to be able to "mute" the jirabot.

1 answer

1 accepted

0 votes
Answer accepted
Daniel Eads
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 28, 2020

Hey Jitu, welcome to the Community!

My suggestion would be to slightly tweak what's configured right now. I'm thinking that maybe you've got personal notifications set up (managed with /jira notify) and the direct messages from the Jira Cloud app are distracting. Is that right?

Given that you already know about muting channels, my suggestion is to disable the personal notifications and instead use channel subscriptions to a new channel in Slack. With a channel specifically for Jira messages (you could create a private one and invite the bot), you won't be seeing other "real" messages from teammates. The channel can be muted in your Slack client so that you can just check it as you please, as you've described.

Does that make sense? I'm happy to clear up questions about the project/channel subscriptions in Jira if you need help getting it set up.

Cheers,
Daniel

Jitu
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 4, 2020

Thanks for quick response and a good enough workaround.

I had to play with it a bit to get equivalent behavior. Still do not covers all the case like (any ticket which I have modified in any way in the past), but good enough.

One need to do the following on "Slack integration" for the repo under interest.

For issues that match the filter:

(watcher = <name do not work but hexadeciaml atlassian id does>) or (assignee was <hex id>) or (reporter= <hex id>)

SEND A MESSAGE TO THE CHANNEL WHEN:

Need to select EVERYTHING..they get applied cumulatively as a massive OR 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events