Hey all,
I'm having notifications from our slack integration across the board created a duplicate notification when an issue is created.
Here are some of the troubleshooting steps already taken from my side.
as far as I can there there have been no changes to the app via upgrade or upgrades on slack either. Any and all help is appreciated.
Hey, folks!
We determined that this was caused by an unannounced change in Slack's REST API response which was not being handled gracefully by the plugin.
To help with this, we released a new version of the Slack for Jira (Official)!
While version 3.0.2 is not yet a permanent fix, it will prevent the duplicate messages from happening.
Atlassian Marketplace - Jira Server for Slack (Official)
Just like its previous version 3.0.1, it is only compatible with Jira version 8.9.1 and newer.
We'll keep adding any future updates on the ticket @Tim Howard kindly provided earlier:
Cheers!
Hey, folks!
We determined that this was caused by an unannounced change in Slack's REST API response which was not being handled gracefully by the plugin.
To help with this, we released a new version of the Slack for Jira (Official)!
While version 3.0.2 is not yet a permanent fix, it will prevent the duplicate messages from happening.
Atlassian Marketplace - Jira Server for Slack (Official)
Just like its previous version 3.0.1, it is only compatible with Jira version 8.9.1 and newer.
We'll keep adding any future updates on the ticket @Tim Howard kindly provided earlier:
Cheers!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Will there be a fix for JIRA Server 8.8 ? This v3.0.2 seemed to be only for JIRA 8.9 up
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Upgraded to v3.0.2 this morning which fixed this but 3 hours later... it's happening again, any advice please?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Filipi Lima
I am using slack 4.29 version with jira cloud. but still am receiving duplicate notifications for every changes. it filling my channel threads...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I just got an answer to my support ticket with Atlassian. This appears to be a bug as Slack updated their API and the Slack for Jira app doesn't handle the response.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for opening the JRASERVER bug!
Here's the response I received from my support request:
We have been receiving dozen of cases regarding this issue since last Friday and an outage alert has been put in place as we gather all possible information from the specific cases and affected version while development and engineering investigate.
We will keep you informed as the information becomes available.
Looks like they're on it :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
+1
Started October 13th, 2022 after 5pm EST.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same here +1
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
same here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you're having the Duplicate Jira Server Messages in Slack problem and can open a Support Request for Jira Server with Atlassian, I encourage you to open a support request!
https://support.atlassian.com/
That will be the best way to get visibility to this problem in order to get it fixed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We are also seeing duplicate announcements, but only on new integrations defined this week. Integrations that were defined prior to this week are all working as expected. We are on an older version of the plugin - 2.0.21. We believe it is a problem on the Slack side, not the Jira side, and have reported it to our partners at Slack. No response from Slack yet.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Slack responded that we need to report the problem to Atlassian since they are the creator of the integration. Atlassian will need to work directly with Slack to determine if there is a problem with the integration. I suggest that everyone on this thread submit a support ticket to Atlassian, citing this conversation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Also having this issue across all projects that use slack.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In the same boat.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Also have the same issue
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
<delete please>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So when an issue is created, 2 identical notifications are send to the same Slack Channel right ?
What are you using to send slack from JIRA ?
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Greetings,
same issue as @Vivo Bandito -- started happening today.
On my setup, 2 out of 11 Jira projects are exhibiting such behaviour.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same issue, started on the 13th. No changes to config or apps. When I re-added the notification I even got a duplicate message: "<user>
We're using Atlassian's Slack plugin for Jira Server
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I've not review it yet but if you are 3 having the issue starting today without having updated anything I would check on Slack side 😅
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We are also having the same issue, I deleted and rebuilt some of our notifications but this did nothing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We have encountered the same issue using the latest version Jira Server for Slack version 3.0.1. I noticed this behavior a few months ago but it happens randomly, but last Oct 12, 2022 it happens to all subscription.
One thread was updated who encountered the same issue Duplicate messages on Slack when creating tickets.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
+1
We're experiencing the same behavior.
Using https://marketplace.atlassian.com/apps/1220099/jira-server-for-slack-official?tab=overview&hosting=datacenter plugin.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We are also having the same issue
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
+1
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Base on the number of impacted user and the fact that the app did not had any update on JIRA side for a while I would reach out to Slack for this issue.
I'm not familiar with this app but do you have a way to get the webhook that is call on Slack side and try to send something from the command line to see if there is the issue ? If so we can definetly remove JIRA from the equation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Florian Bonniec
It's not a Slack problem. It's the Jira Server App - https://slack.com/apps/ADZHDM3L1-jira-server - which is an Official, supported Atlassian Slack Application.
I've just now opened a support request with Atlassian and uploaded a Support Zip so that should get the ball rolling internally if no one else has done that yet.
I spent a few hours today parsing through the logs - it's crystal clear that the Jira Server for Slack Plugin - https://marketplace.atlassian.com/apps/1220099/jira-server-for-slack-official - is sending one (and exactly one) Slack message to the Slack App API endpoint, which then results in two (exactly two) messages for each and every event.
This is quite plainly out of the hands of the users, as we do not (and cannot) have any control over the Slack App (which is entirely owned and managed by Atlassian).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Jira Server for Slack (Official) v3.0.2 resolves this problem (released 17.10.2022)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How is this even possible... and how can it be "fixed" by a patch which didn't broke it in the first place!?
We haven't changed anything on the Jira server, nor the plugins in the last few weeks and suddenly we are experiencing this issue as well.
Unfortunately we are currently still at a pre- Jira Server V8.9.1 version of Jira Core (long story don't want to go into), meaning we run slack app V2.0.23 and can't "fix" this, because there is no "fix" in the previous slack plugins?!
I'd like to better understand the cause of the issue and know if there are workarounds?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, @Hylke,
I'm sorry to hear you're unable to upgrade into a Supported version.
The event that we believe triggered this problem is not on your instance or due to any change under your control.
Apparently sometime last week, the response our plugin gets from Slack changed slightly in format in a way that our plugin could not handle it gracefully, leading to a retry and the duplicate message.
It started sending a "rich_text" element within "blocks" which was not expected.
At this time, we do not have plans to create a fix for an older and unsupported version - Jira 8.9.x itself reached End of Life on May 2022.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Filipi Lima We are seeing this same issue, but are running version 3.0.3. Is it possible it is not actually fixed?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, Chad, version 3.0.3 has the permanent fix for the duplicate messages caused by the unexpected elements coming from Slack's response.
I recommend checking if you have multiple subscriptions for the same event and also try a test on a dedicated channel for a test issue/project.
If it remains unclear, you may open a ticket on https://support.atlassian.com/contact/ so we can check it in more details.
Cheers!
Filipi Lima
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.