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

when assignee changes, previous assignee would prefer NO email notification, unless issue is already "In Progress"

    XMLWordPrintable

Details

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      complaint from our users:

      I don't want a notification email when someone else gets assigned

      Is it really important to send this kind of mails?
      I am not watcher, nor in copy to, not reporter.
      So the reason I received this mail, was because I was Assignee, but not anymore and someone else has changed that.
      So I don't have to do anything anymore,
      so I should not receive this update from JIRA by mail:

      ----- Forwarded by LV@.... on 31/07/2011 11:27 -----
From:	"SH (JIRA)" <noreply@...>
To:	LV@...
Date:	28/07/2011 23:10
Subject:	SILKROAD Assigned: (SR-1329) Main icons - Blue




     [ http://..../browse/SR-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

SH reassigned SR-1329:
------------------------------------

    Assignee: JB  (was: LV)

...

      Proposed solution

      I think the email notification scheme needs to be extended to the user profile & so that users can select which events they want to be notified of. Ideally these settings should also allow for conditional rules. (such as the above mentioned unless issue is already "In Progress" )

      Attachments

        Issue Links

          duplicates

          Suggestion - JRASERVER-2565 Rule-based Notification Schemes

          • Gathering Interest
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-22106 Sending notification to previous assignee even setting "jira.assignee.change.is.sent.to.both.parties" to false

          • Medium - Medium priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-25926 "jira.assignee.change.is.sent.to.both.parties" Properties doesn't take effect after modify via jira-config.properties and jpm.xml.

          • Low - Low priority issues
          • Closed
          relates to

          Suggestion - JRACLOUD-26025 when assignee changes, previous assignee would prefer NO email notification, unless issue is already "In Progress"

          • Closed

          Activity

            People

              Unassigned Unassigned
              43d7e8d94038 bede
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: