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

Adding a comment to an issue from the List View triggers duplicated notification/message

    XMLWordPrintable

Details

    • Bug
    • Resolution: Timed out
    • Low
    • None
    • 7.2.7, 7.4.0, 7.3.7
    • Project - Issues
    • None
    • 7.02
    • 1
    • Severity 3 - Minor
    • 1
    • Hide
      Atlassian Update – 12 February 2020

      Hi everyone,

      After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out.

      Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy.

      To see what the Jira team is currently working on and has recently delivered see the following dashboards:

      We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments.

      Thank you,
      Jira Server Bug Fix team

      Show
      Atlassian Update – 12 February 2020 Hi everyone, After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out . Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy . To see what the Jira team is currently working on and has recently delivered see the following dashboards: Jira Server and Data Center: Recently resolved issues Jira Server and Data Center: Current work and future plans Jira Server and Data Center: Bug Fix Board We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments. Thank you, Jira Server Bug Fix team

    Description

      Issue Summary

      Adding a comment to an issue from the issue navigator, in 'List View' mode, it triggers duplicated notification/message.

      Steps to Reproduce
      1. Perform any search in the issue navigator
      2. Switch to List View
      3. Use the "..." option on the right side of the screen and select "Comment" (doublemessage01.png).
      4. Add any comment (doublemessage02.png).
      Expected Behavior
      • The message is added and JIRA shows a incoming message at the top right corner indicating the user that the issue was updated.
      Actual Behavior
      • The message is added but JIRA shows a duplicated incoming message at the top right corner indicating the user that the issue was updated (doublemessage03.png).
      Cause
      • Unknown.
      Workaround
      • None.
      Notes:
      • Browser independent (tested in Chrome 59, Firefox 52 and MS Edge 40 MSEdge_doublemessage.png).
      • Seems to be independent from Notification scheme, as this was tested with diferent combinations of being/not being the assignee, being/not being the reporter and being/not being a Watcher.

      Attachments

        1. doublemessage01.png
          doublemessage01.png
          87 kB
        2. doublemessage02.png
          doublemessage02.png
          65 kB
        3. doublemessage03.png
          doublemessage03.png
          76 kB
        4. MSEdge_doublemessage.png
          MSEdge_doublemessage.png
          56 kB

        Activity

          People

            Unassigned Unassigned
            rchiquete Rene C. [Atlassian Cloud Support]
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: