duplicating comments

[vandr0s]

Good day.
We have using mattermost-jira service desk datacenter integration fot a long time with no issues. At the end of the previous year we have updated our jira service desk instance to version 10.x. After that we encountered duplicated comments from jira bot in channels. Every other notifications, like status updates posts normal, but every comments-related events duplicating in every channel. I have tried to recreate subscriptions from scratch, update plugin to version 4.2.0 and jira to latest version, but nothing helps. Can i have some assist?

[Kshitij-Katiyar]

@vandr0s
Sure, just one request. Can you please upgrade your plugin to v4.2.1? Also, can you check if duplicate webhooks are created on the Jira side? If yes, please delete the older ones

[vandr0s]

@Kshitij-Katiyar
Thanks for answer.
I have upgraded plugin to 4.2.1, recreated integration following official documentation https://docs.mattermost.com/integrate/jira-interoperability.html#setup (have recreated webhook and app link on jira side, there is only one webhook)
No differences - comments still duplicating

[Kshitij-Katiyar]

@vandr0s Thanks for the efforts. Just a few more requests:

1. Share your Jira server version, Mattermost version and Plugin version(you mentioned it to be 4.2.1 now)
2. Trigger an event on Jira and share the screenshot of the following:

• Event on Jira
• Subscription notification on Mattermost
• Server logs when the event was created and when the notifications where received on Mattermot

[vandr0s]

Jira Service Management 10.3.2
Mattermost Version: 10.4.2
Jira Plugin 4.2.1
I have tried to collect mattermost logs in DEBUG mode, but there is so many of them, i cant find webhooks related.
Then I have collected Jira logs:
2025-03-03 14:59:44,660+0300 webhook-dispatcher:thread-4 DEBUG anonymous [c.a.webhooks.internal.DefaultPayloadManager] Webhook payload has been set by [JiraWebhookPayloadProvider] for invocation [507f559a-5d20-424e-b7c2-0488170d9ce1] 2025-03-03 14:59:44,665+0300 webhook-dispatcher:thread-4 DEBUG anonymous [c.a.webhooks.internal.DefaultWebhookService] The overall result of the filter was [true] for invocation [507f559a-5d20-424e-b7c2-0488170d9ce1] 2025-03-03 14:59:44,665+0300 webhook-dispatcher:thread-4 DEBUG anonymous [c.a.w.internal.publish.DefaultWebhookDispatcher] Starting dispatch work for webhook invocation [507f559a-5d20-424e-b7c2-0488170d9ce1] 2025-03-03 14:59:44,677+0300 ForkJoinPool.commonPool-worker-2762 DEBUG [c.a.w.internal.publish.DefaultWebhookDispatcher] Request has completed for webhook invocation [507f559a-5d20-424e-b7c2-0488170d9ce1]. Status code = 200 2025-03-03 14:59:44,839+0300 webhook-dispatcher:thread-5 DEBUG anonymous [c.a.webhooks.internal.DefaultPayloadManager] Webhook payload has been set by [JiraWebhookPayloadProvider] for invocation [69e1783c-27cf-4e0b-8a61-308507de9cb1] 2025-03-03 14:59:44,844+0300 webhook-dispatcher:thread-5 DEBUG anonymous [c.a.webhooks.internal.DefaultWebhookService] The overall result of the filter was [true] for invocation [69e1783c-27cf-4e0b-8a61-308507de9cb1] 2025-03-03 14:59:44,844+0300 webhook-dispatcher:thread-5 DEBUG anonymous [c.a.w.internal.publish.DefaultWebhookDispatcher] Starting dispatch work for webhook invocation [69e1783c-27cf-4e0b-8a61-308507de9cb1] 2025-03-03 14:59:44,849+0300 ForkJoinPool.commonPool-worker-2762 DEBUG [c.a.w.internal.publish.DefaultWebhookDispatcher] Request has completed for webhook invocation [69e1783c-27cf-4e0b-8a61-308507de9cb1]. Status code = 200
It seems to me that duplication is on Jira side,
I have tried to disable comments in webhook properties, and this fixed the problem, all notifications are now in single copy.
Maybe there is some changes on how Jira Service Desk send notifications via webhooks in 10.x version?

[Kshitij-Katiyar]

@vandr0s
Thanks for the info, we will try to reproduce this issue and fix it if it requires.
Let us know if we can help you with anything for now

[vandr0s]

I think this workaround is ok for us for now.
Thanks for assistance.

[Kshitij-Katiyar]

@AayushChaudhary0001 Please test this issue once