History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: JRA-12789
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: JP Patrikainen
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
JIRA

Possibility choose to send email or not when notification event is triggerred

Created: 25/May/07 05:27 AM   Updated: 21/Aug/07 02:01 PM
Component/s: Email integration
Affects Version/s: 3.9
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Reference
 

Participants: Anton Mazkovoi [Atlassian], JP Patrikainen and Neal Applebaum
Since last comment: 57 weeks, 5 days ago
To be done by: Single developer
Labels:


 Description  « Hide
Hi,

Issue:
Our users would like to have possibilty to choose when they want to send email.

Like when you add comment, they want to choose to sending email like "Send email to... [X]" or not to send ""Send email to... [ ]"

Improvement:
MUST: Is it possible to add this kind of "Send email.." check box below "Viewable by:" field?
WISH: They also would like to see who will get that email.

-JP



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Anton Mazkovoi [Atlassian] - 27/May/07 06:56 PM
Hi JP,

In JIRA the decision about who is going to be notified when a change is made is left for the administrators. This way it is possible to ensure that required users are notified at all times.

Allowing the users who are making the changes to make a decision about who is notified kind of goes against that approach. It might also make new JIRA users quite confused as to what they are meant to do with the notification fields on the e.g. Add Comment screen.

May I ask if adding the functionality of e-mailing an issue to a set of users (or external e-mail addresses) would help you? If so, please vote for JRA-5959, as we are much more likely to implement this in the future than this improvement.

Please let me know what you think.

Cheers,
Anton


Neal Applebaum - 28/May/07 09:42 AM - edited
See related issue JRA-2644. Following up on Anton's comments, JIRA is set up so that an administrator decides what notifications should be generated. If everyone has the same expectations about when an email is sent, that is IMO a good thing. If users are allowed to not send emails or receive emails under certain conditions, then it can lead to situations where the author of a comment or change might have expected JIRA to notify someone and not follow up via email, where the recipient actually never received it in the first place. In my opinion, it's better to send the email and let the recipient decide whether to ignore it or not. I said the same thing over at the linked issue, although I can certainly see value in suppressing emails on minor edits and for certain users to prefer not to receive emails. Tough to satisfy everyone, I guess. Maybe the solution is to go forward with the ability for users to customize their email preferences as long as the JIRA administrator has given them that permission.

Anton Mazkovoi [Atlassian] - 31/May/07 07:13 PM
JP,

I would be very interested to hear your thoughts on Neal's and my feedback.

When you have time, please let us know what you think.

Cheers,
Anton


JP Patrikainen - 12/Jun/07 09:18 AM - edited
Hi Anton & Neal,

Here is a few scenarios:


First

Well .. now I read that JRA-5959 and that would be the solution for this Fistr one.

We have quite tight security settings.. e.g.

4 security levels

  • Public
  • Confidential
    • everybody in Customer-group can see
  • Company Confidential (default)
    • customer can see own (if they are in reporter, assignee)
  • Secret

Sometimes we have to send comments to many customers than assignee+reporter (let's call then CC-users), but we do not want to drop security level.

E.g. following situation.

  • first customer creates issue
  • it is assigned to antoher to get implementation approval
    -> when it is assigned back to us the second customer does not get comments anymore

One resolution:

  • First idea was that we can add CC-users to watcher -list: does not work, because security level blocks them out
  • Second idea was that let's add Watchers-"group" to Company Confidentil -security level: +it is not possible to add "Watchers" to security level

Could it be possible to add similar list like "Watchers", where manager user (how has rights to add people to this list) could add these CC-users. Then it would be possible to add this "Users in CC-list" to security level.

Would this be something that you Neal you thought?
Administrator gives basic rights ("Users in CC-list") and End user can use list, if she/he has rights to add another users to list.

Hopefully you got my idea?


Second

  • I am a developer and we have customer reported issue.
  • I'm writting a comment and I will save it.
  • I notice that a reporter is a customer!!

A few usability problems (see Ten Usability Heuristics :http://www.useit.com/papers/heuristic/heuristic_list.html)

  • "Visibility of system status"*
  1. Developer does not know who will get mail
    "User control and freedom"
  2. Developer does not have a change to choose to send or not to send notification

One resolution:
after save there should be confirmation for sending email

  • shows list users to whom it will be sent
  • gives user possibility choose not to send

Administrator could give this viewing/choosing right to user/group/role/...

BR,
-JP


Anton Mazkovoi [Atlassian] - 12/Jun/07 05:03 PM
Hi JP,

Thanks for the update. I am glad that JRA-5959 will address some of your requirements.

I will leave this issue open to track the requirements of your second scenario. However, please note, that as I have mentioned earlier this approach does go somewhat against the JIRA's policy to notifications, where administrators control who is notified of what events. I do not think we get a feature such as this one requested very often, and therefore we will have to see how much interest it attracts.

Cheers,
Anton