-
Bug
-
Resolution: Fixed
-
Low (View bug fix roadmap)
-
6.3.10, 6.3.12, 6.4-OD-14
-
6.03
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Summary
In the notification scheme, no one is set to receive Issue Updated, but users are set to receive Issue Commented. When a comment is added via email, nobody gets notification. When a comment is added via UI, they get notification for Issue Commented.
After some testing I found that commenting via email will trigger Issue Updated, that is the reason users don't receive notification even though they are supposed to receive for Issue Commented. By right commenting via email and UI should behave the same and trigger Issue Commented and users should get notification.
Steps to reproduce
- Install JIRA
- Configure Incoming Mail Handler (Create a new issue or add a comment to an existing issue) and Outgoing Mail
- Remove everyone from Issue Updated event but make sure they receive notifications from Issue Commented event
- Have a user add a comment to a particular issue via email
Expected Results
- Comment added successfully
- Designated users receive notification
- Notification sent with Issue Commented event
Actual Results
- Comment added successfully
- No notification received by users who supposed to receive Issue Commented event
Notes
- When the users are configured to receive notification from Issue Updated event, then commenting via email will send notifications to the designated users
- Affecting with JIRA 6.3.10 and 6.3.12
- With 6.2.7, notification will be of Issue Commented event (intended behavior)
- derived from
-
JRASERVER-39087 Notifications of new comments not being sent out if comment comes from a reply to an email notification
-
- Closed
-
- relates to
-
JRACLOUD-41226 Comments From Email Trigger Notifications for "Issue Updated" Instead of "Issue Commented" Event
-
- Closed
-
- is related to
-
JSP-216030 You do not have permission to view this issue
Hi all / andrea.turati / evangelos.vrocharis / andistuttgart / dl-vendors,
This is a resolved issue, and as far as we know, it has not regressed.
Consequently, I heavily suspect that you are observing a related but different problem in your instance. In order to be able to help you further, could you please get in touch with us via a support ticket at https://support.atlassian.com so we can look further into the particular problems in your instances.
Furthermore, resolved issues are not actively triaged. If you think you are being affected via a resolved issue, please do get in touch with us at https://support.atlassian.com so we can help and confirm what is happening.
Regards,
Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].