-
Bug
-
Resolution: Fixed
-
Medium
NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.
Hi everyone,
Thanks for your votes and feedback on this bug report.
We are happy to announce that this work has already been completed and that the issue has been resolved for JIRA 6.3.10 and later versions.
Customers using the workaround to disable inline edit are encouraged to enable this feature again for an improved user experience after upgrading.
Thanks a lot for your patience and we hope you appreciate our open approach to bug reports and suggestions.
Regards,
Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].
Summary
When the user edits the Assignee using the Edit screen or the new Inline Editing feature, it triggers an Issue Updated event.
It would be better to trigger the Issue Assigned event whenever the Assignee is changed, no matter how it was changed.
Workarounds
- Disable In-line editing for Assignee field - https://confluence.atlassian.com/display/JIRAKB/How+to+Disable+Inline+Edit+for+Assignee+Field
- Use the 'Issue Updated' event for notifications, as that event is triggered instead.
- is duplicated by
-
JRACLOUD-12362 Fire all notification scheme events regardless of whether or not other events have been activated
- Closed
-
JRACLOUD-32106 Editing the assignee field should be considered as Issue Assigned Event
- Closed
- is related 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
-
JRACLOUD-12362 Fire all notification scheme events regardless of whether or not other events have been activated
- Closed
- relates to
-
JRACLOUD-2565 Rule-based Notification Schemes
- Gathering Interest