Details
-
Bug
-
Resolution: Won't Fix
-
High
-
None
-
3.5.1
-
3.05
-
Description
A project has a notification scheme that has the default entry for "Issue updated" but all notifications for "Issue Resolved" are removed.
If the issue is resolved, and at the same time the issue is assigned to somebody else, no email is sent.
This is certainly incorrect because the result is different from what would happen if both actions are performed in two separate steps (either resolve first, then assign; or assign first, then resolve). The assignee would receive his email in this case, but not if everything is done at once.
JIRA should try each notification rule for all affected actions, not just one rule.
This is a critical problem because the customer relies on email for his internal workflow, so important tasks such as regression tests never start because the assignee does not get the notification email. Customer is quite upset.
This problem also exist in earlier JIRA releases.
Attachments
Issue Links
- is related to
-
JRASERVER-8493 No notification sent when issue re-assigned via bulk edit
- Closed
- relates to
-
JRASERVER-12362 Fire all notification scheme events regardless of whether or not other events have been activated
- Closed