-
Bug
-
Resolution: Fixed
-
Medium
-
6.3.10, 6.3.11, 6.3.12
-
6.03
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Hi everyone,
We expect a fix for this issue to be released in early January for both JIRA Cloud and JIRA Server.
We will update the current behavior to remove the association between Issue Worklogs and the Issue Updated event. This should resolve the problem originally described in this issue.
As I mentioned in my previous update, improving events and email notifications is part of the current JIRA roadmap. A number of you have indicated that there are existing challenges you face with JIRA email notifications beyond this issue. We would love to hear your feedback and suggestions – feel free to contact me directly.
Thanks,
Dave
Product Manager - JIRA Platform
Steps to reproduce
- Remove all log work notification
- Have the user create an issue (PROA-4 in my test)
- As an admin, log work on the issue
Expected Results
- No email notification received by reporter
Actual Results
Additional
- is duplicated by
-
JRASERVER-41084 Work logged on issue seems to be treated as generic event
- Closed
-
JRASERVER-41110 When logging work, users are getting notifications when logged work is off
- Closed
- relates to
-
JRACLOUD-41046 Logging work sends email even if not configured in notification scheme
- Closed
-
JRASERVER-29328 Editing Assignee should trigger 'Issue Assigned' event
- Closed
- was cloned as
-
SW-1258 Loading...