How to disable Slack channel notification for Jira edit comment?

[DHSV]

Somehow we figured out how to disable Description editing notification (since it prints the entire description in the notification no matter what's edited), but I can't seem to find a way to disable it for comment editing...

We want a notification on a new comment (though it doesn't need to show the whole comment in the notification for crying out loud), but not when it's edited. Sometimes we just make typos or corrections, but the channel gets glutted with Jira sending too much info (diff change lines using green and red might be nice though, like I got in emails with the old Jira).

Am I missing something here or is Jira right now not capable of disabling comment edit notifications to Slack or not programmed to truncate the comment in the notification?

Note: the settings I'm talking about are in the Project Settings > Apps > Slack Integration > Edit (for the channel) - see attached screenshot.

[Joris Vleminckx]

Hmm, I note that any edits, even directly after adding a new comment are sent too slack, causing noise. :/ 

Any chance to enforce the behaviour as describe above?

[Joris Vleminckx]

I created an issue: https://jira.atlassian.com/browse/API-105

Please vote!

[Marty]

Hi Dave,

I am not in the team that built the Jira <-> Slack integration but I reached out to them.

For now the expected behaviour is that it does send a notification about the first comment edit after the comment has been created but then don’t send any notifications for an hour, even if the comment is edited. This is intended to reduce the noise in the channel. 

I'd recommend going to our public issue tracker and raising a feature request if you'd like to see different behaviour: https://jira.atlassian.com/projects/API/issues 

[DHSV]

So after an hour, editing the comment again will send the entire comment to Slack?

[Marty]

If a new edit is made after an hour then yes

[DHSV]

Looks like the Atlassian issues board uses the old-gen format.

[Marty]

lol

I think we're too busy shipping to customers right now but I think we will eventually move jira.atlassian.com to a next-gen project

[DHSV]

Should we be using the old-gen boards like the Atlassian development team does?

We're using what was installed on default after we started paying, which was next-gen... I'm curious why the dev team is still using old-gen.

We'd like a lot of stuff in old-gen but also the pop-up ticket windows of new-gen... this doesn't seem possible. Maybe I'd recommend not defaulting customers to next-gen until the Atlassian development team is also using next-gen for their own development of Jira.

[Marty]

Hi Dave,

we are using next-gen for plenty of things including internal development.  For example, my team is using next-gen.  We just haven't gotten around to moving our public bug tracker to next-gen yet.  

[DHSV]

Seems like the public tracker should have been the first thing to be next-gen when the customers were defaulted to it. Just sayin'. Otherwise it looks like Atlassian really isn't taking their next-gen project format to heart.