Jira Plugin Sends Duplicate Assignment Notifications in High Availability Environments

Applies to: Mattermost Jira Plugin v4.7.1 and earlier; Mattermost HA cluster deployments; Jira Data Center and Jira Server.

Symptoms: Users receive two identical Jira assignment DMs in HA Mattermost environments.

🛑 Problem

Jira Data Center fires two webhook events simultaneously for a single assignment (issue_updated and issue_assigned). In an HA cluster, these hit different Mattermost nodes at the same instant, bypassing the per-node dedup check. Each node sends a notification independently. Specific to HA; single-node deployments unaffected.

✅ Solution

Permanent fix: Upgrade to the upcoming Jira plugin release including PR #1321. Fix is merged.

Workaround (Jira Cloud / Jira Server only): In Jira webhook config, uncheck "Issue Assigned", keep "Issue Updated" checked.

⚠️ Jira Data Center does not expose "Issue Assigned" separately — the plugin-side fix is the only solution for DC.

Diagnostic Steps

The EnableWebhookEventLogging setting for the Jira plugin allows for webhook events to be sent to the file logs. The logs should then show how many times Jira actually delivered the event to Mattermost to confirm the duplicate deliveries.

Enable webhook event logging:

mmctl config set PluginSettings.Plugins.jira.EnableWebhookEventLogging true

Reproduce an assignment, check logs. Disable after:

mmctl config set PluginSettings.Plugins.jira.EnableWebhookEventLogging false

Additional Resources

• Jira Plugin Releases