Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-69453

Users receive duplicate notifications when mentioned in issue comments

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • High
    • None
    • 8.0.0
    • Mail Server
    • 8
    • 9
    • Severity 3 - Minor
    • 26
    • Hide
      Atlassian Update – 15 July 2019

      Hi everyone,

      We've discovered that this issue has been duplicated by the issue at https://jira.atlassian.com/browse/JRASERVER-69137. I am glad to inform you that the solutions will be available from Jira 8.3. Please watch that issue for further updates.

       

      Cheers,
      Mateusz
      Jira Server Team

      Show
      Atlassian Update – 15 July 2019 Hi everyone, We've discovered that this issue has been duplicated by the issue at  https://jira.atlassian.com/browse/JRASERVER-69137 . I am glad to inform you that the solutions will be available from Jira 8.3. Please watch that issue for further updates.   Cheers, Mateusz Jira Server Team

    Description

      Summary

      Jira is sending duplicate notifications when batched notifications are enabled and users are mentioned.

      Steps to Reproduce

      1. Have batched notifications enabled for a project.
      2. Leave a comment on an issue with a mention directed at my user name.
      3. Take no other action on this issue for at least 20 minutes.

      Expected Results

      An email notification about the mention is received, and no other email notifications.

      Actual Results

      An email notification about the mention is received, and later an additional email notification with batched changes is sent.
      Suggested Solution

      Workaround

      No workaround available.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              nparks@atlassian.com Nathan Parks
              Votes:
              24 Vote for this issue
              Watchers:
              25 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: