Details
-
Bug
-
Resolution: Duplicate
-
Medium
-
None
-
4.1.2
-
4.01
-
Description
According to this bug report (http://jira.atlassian.com/browse/JRA-6344), since JIRA 4 when the assignee is changed, a notification is sent to previous and current assignee.
Also, for those people who do not like this new behavior there is a new jira-applications property to revert to the old behavior.
jira.assignee.change.is.sent.to.both.parties=false
The problem is that if you need to fire "Issue Assigned" event by a post-function. The notification will ignore the "jira.assignee.change.is.sent.to.both.parties" parameter, i.e, it will always send email to previous and current assignee. The expected behavior would be to send notification respecting the value passed to that parameter.
Although, if you fire a custom event by a post-function, the notification will respect that parameter, i.e., using custom event, it'll work as expected.
Attachments
Issue Links
- is duplicated by
-
JRASERVER-25926 "jira.assignee.change.is.sent.to.both.parties" Properties doesn't take effect after modify via jira-config.properties and jpm.xml.
- Closed
- relates to
-
JRASERVER-26025 when assignee changes, previous assignee would prefer NO email notification, unless issue is already "In Progress"
- Closed