[#JRA-9397] Bulk change assignee doesn't send emails to Issue Assigned events

JIRA

Bulk change assignee doesn't send emails to Issue Assigned events

Created: 20/Feb/06 03:07 AM Updated: 12/Mar/07 05:52 PM

Component/s:

Bulk Operations

Affects Version/s:

3.5

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Duplicate

This issue duplicates:

~~JRA-8493~~ No notification sent when issue re-assigned via bulk edit

Reference

This issue relates to:

JRA-12362 Fire all notification scheme events regardless of whether or not other events have been activated

Participants:	=Neal Applebaum, Arne Schirmacher, Joachim Marwinski and Mark Chaimungkalanont [Atlassian]
Since last comment:	2 years, 27 weeks ago
Labels:

Description

« Hide

The Notification scheme has the entries

Issue Updated
Issue Assigned	Current Assignee, Reporter

If User 1 assigns a single issue to User 2, User 2 gets a notification email.

But if User 1 uses the bulk edit feature from the navigator to assign several issues to User 2, he does not get a notification email.

It seems that the bulk change is considered only an issue update, not a change assignee.

I think this is a bug ar at least a problematic inconsistency. The assignee should get an email regardless of whether it has been triggered by a single action or by a bulk change. My customer relies on the emails being sent to the respective developers. If emails do not arrive, or if the send email notification feature is unreliable, it looks as if the developers are lazy and this is a severe problem.

This issue affects probably also earlier releases than 3.5, but I don't have test environments available right now.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

=Neal Applebaum added a comment - 20/Feb/06 08:37 AM

I already reported this as a bug as well, Arne. See linked issue.

[ Permlink | « Hide ]

Mark Chaimungkalanont [Atlassian] added a comment - 20/Feb/06 05:56 PM

I think this is a bug ar at least a problematic inconsistency

I'd tend to agree here although this isn't a problem with bulk change as such, but a general problem with the "Issue Asigned" event. The only time this event is fired, is when you use the "Assign" operation, editing a single issue and changing the assignee will not fire the "Issue Assigned" event but only fire the "Issue Updated" event.

As Jeff pointed out in ~~JRA-4949~~, this "is how it's always worked". It is very counter intuitive however, so we should at the very least document this inline so people know what's going to happen when they choose the "Issue Assigned" notification. If possible, however, a special check should be made to see if the assignee field has changed, and if so, fire off the "issue Assigned" notification event.

[ Permlink | « Hide ]

Joachim Marwinski added a comment - 21/Feb/06 05:55 AM

I refer to a configuration in which the workflow leads the user through the process.
All "ordinary" user are instructed to use only the workflow-actions, not the standard actions. Depending on the workflow, a status may have the available actions

..
assign to teamlead
assign to department lead
back to client/initiator
work on issue
..

The underlying workflow transitions show different screens, one of the fields is the "assign to" field.

It is important to have an "issue assigned" notification, which is different form an "issue updated" notification, as it is <b>only</b> fired if an issue is assigned to a <b>new</b> assignee.

From the moment that the assignee gets informed that he has to work on the issue, he can watch the issue and every change whithout the need to be informed immediately after a change.

If an assignee is assigned to issues only from time to time, maybe after a period of two weeks, he does not look into JIRA every day. In this case he needs to be notified that he is assigned, but he does not need further notification on every change.

In the example (described above), a client needs to be notified that some questions occured regarding his issue. The clients usually do not ~~or only occationally~~ look into JIRA, but in some cases their comments are needed.
They can not be notified by email, except we notify the current assignee of all changes, which would cause lots of unwanted emails -to the developers. They are often / during a long time assignee, they look into JIRA every day. --> Developers don't need the "issue updated" emails.

[ Permlink | « Hide ]

=Neal Applebaum added a comment - 21/Feb/06 11:13 AM

If possible, however, a special check should be made to see if the assignee field has changed, and if so, fire off the "issue Assigned" notification event.

Exactly.