-
Bug
-
Resolution: Fixed
-
Medium
-
3.0.3
-
tomcat 4.1.30, sql server 2K, fedora core 1, jira enterprise 3.0.3 build 75
-
3
-
zFrom what I can tell there are 4 different ways to 're-assign' an issue via the JIRA web interface:
1) select 'assign' this issue
2) select 'to me' (part of 'assign this issue (to me)' option
3) edit the issue and change the assignee
4) bulk edit the issue and alter the assignee
The third option fails to send an email notification to the previous 'assignee' saying that the issue has been re-assigned. Notifications to both the new 'assignee' and 'reporter' are sent.
The other options above all send notifications to all 3 parties - the previous 'assignee', the new 'assignee' and the 'reporter'. All users in question have their profile set to receive notifications of changes they make. In all four cases above the issue reporter made the change to the issue.
I believe this to be a bug.
- has a regression in
-
JRASERVER-26898 The notifications are not sent when bulk assigning issues
- Closed
- is duplicated by
-
JRASERVER-5181 Assignee Change on "Edit Issue" - no notification is sent to the new assignee.
- Closed
-
JRASERVER-23553 Email Notification Issue not working
- Closed
-
JRASERVER-9397 Bulk change assignee doesn't send emails to Issue Assigned events
- Closed
- is related to
-
JRASERVER-9238 Bulk Change Issue Assignee (even for closed/uneditable issues)
- Closed
-
JRASERVER-14052 Notification scheme can set "Previous Assignee" and "Current Assignee"
- Closed
- relates to
-
JRASERVER-8819 An issue moved into a project is not seen as a Created Issue in the target project from a notification perspective.
- Closed
-
JRASERVER-12362 Fire all notification scheme events regardless of whether or not other events have been activated
- Closed