Thilinia, it worked

test comment

Wyatt, what you're describing sounds like correct behaviour to me, even if for your particular use case it's not desirable.

Issue Updated event fires when any field is updated. Someone updated the Assignee field, which is an update, so the Issue Updated event fires.

It sounds like you're saying the Issue Updated event should ignore the Assignee field, since that field has its own special event. Were Jira to be developed from scratch, I'd agree with you. But making the change you're suggesting now would interfere with at least some customers who expect the Issue Updated event whenever an issue is updated if any way.

You might be able to craft a custom solution using Jira Script Runner (now a paid add-on). It has a feature called Script Listeners, one of which is "Fire an event when condition is true". You can set up your Notification Schemes to ignore the standard Issue Updated event, and create a Script Listener for it, and then create your own new event called IssueUpdatedNew. For the script, you can check if the only field changed was the Assignee field, and if that is true, then don't generate any event. Otherwise, if at least one other field was changed, then generate an IssueUpdatedNew event, and set up your notification schemes to listen to that event.

Documentation for ScriptRunner listeners: https://scriptrunner.adaptavist.com/4.3.1/jira/listeners.html

Hi Oswaldo, I am running into what seems to be the opposite issue. When I update the assignee I DO NOT want to send a notification to the reporter. I have disabled reporter notifications for the "Issue Assigned" event, however, the system is registering the update to the assignee as an "Issue Updated" event as well, which then sends notifications out. I don't want to disable notifications for "issue updated" events, but I want to disable them for the "issue assigned" event. Any suggestions?

Thank you for the response, Oswaldo. This was exactly my understanding. As we are running v6.4.5 i will file a separate support request.

Hi olga.sachenko,

This was fixed in JIRA 6.3.10. If you are running and older version of JIRA, you will need to upgrade your instance.

Otherwise, this should not be causing a problem anymore, if that's the case please do file a support request with us at https://support.atlassian.com so we can help you further troubleshoot what is happening with your instance.

Thanks.

Regards,

Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].

We are having the same issue as Lance Wong. We need to trigger a scripted action relying on the Issue Assigned event. It works perfect with "Assign" button and "Assign to me" link. But nothing happens when users edit assignee inline.

This is critical as in most cases users prefer easy inline edit and our workflow breaks.

Hi yee.hou.gan1736594191,

This issue was indeed fixed in JIRA 6.3.10. If you are still having issues with your JIRA instance, could you please raise a support request with us at https://support.atlassian.com so we can help you further.

Regards,

Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].

Hi
I just want to get the updated answer whether this problem has been solved?
Based on my project configuration, watchers should receive email when a ticket assigns to somebody.
But, in fact, watchers do not receive any email from Jira.

Thanks

referring to comment 09/Jun/2015 7:13 AM, we are experiencing the same thing. Using v6.4.11 when the assignee field is edited inline, although JIRA sends out an email that says the issue was reassigned, the actual EventType that we captured was EventType.ISSUE_UPDATED_ID which is what i thought this whole topic was about...