Home      FAQ      Idea Exchange      Ask a Question      My Stuff      Help   
  
Allow users more control over when to be notified
Many users don't need to be notified of the details occuring within the process of resolving an issue. Need to be able to set an option to either notify when assigned to "Me" or resolved / closed. To much of what the users call spam is getting emailed.
ID
179
Category
User Interface
Author
Ron Fox
Date Created
5/16/2007 10:16:07 AM
Date Updated
4/16/2010 10:33:26 AM
Status
New Idea
Score
40
Promoted By
Matthew HesseMiguel BerrozpeCaroline Berrie
Ron Fox
Comments
Barbara Bernardin 5/16/2007 2:54:31 PM
I don't know that I want the users making this call - if they select not to be notified and yet I think they are, then there could be problems. One possibility is to have an admin setting indicating that individual users are allowed to determine when they should be notified. I think it would also help to have some of the functions combined so that you don't have to do multiple steps and cause multiple emails to be sent. For example, when I resolve an issue, I may want to reassign it and/or change the phase. I do not have the option of doing anything once I click resolve other than adding a commnent. I would like to be able to do other edits as well.
Ron Fox 5/16/2007 7:06:45 PM
The administrator should have the ability to determine who gets notified and at what steps. Currently users can set a preference that stops their email notifications.
Evgen Goncharov  Staff  5/17/2007 5:06:52 AM
Actually BUGtrack already have quite flexible notification settings for both administrator and users.

Administrator can specify different 'Notifications Scheme' for each role.
For newly created roles notifications are sent for all actions on "related records", i.e. users that somehow participated with record will receive notifications on any subsequent action.
That can be easily changed to notify only on assign, resolve and close actions (as described in idea) by editing particular role and disabling notifications on other actions and adjusting remaining actions scope in 'Notifications Scheme' section.

Users can alter scheme defined in roles for individual records by following "Change" link in 'Notify' row while viewing record.
Also notifications can be completely disabled in Preferences.

Miguel Berrozpe 1/3/2009 1:46:16 PM
Although I already got some related replies from Evgen (from Bugtrack support), personally I promote the idea of a fundamental improvement in BugTrack's e-mail notification scheme on a "per-issue" ("per-bug") Dstribution Lst basis.

Per principle, it should be possible to assign a specific Distribution List to each bug or issue. This is the way most human organizations work (i.e. we all have managers, customers, staff departments, or otherwise stakeholders, who -rightfully- want to be informed of the progress of a specific issue or topic. And the worse of it, we are -rightfully- blamed, if they are not so informed).

To respect BugTrack's scheme of roles and accessibility or visibility to different users, every person in a bug's distribution list would of course only get the notifications as authorized by their position in BugTrack's "Role" scheme.

The BugTrack tech support clarified to me that Bugtrack allows users with "Subscribe" role authorization to INDIVIDUALLY subscribe or unsubscribe from notifications for any specific issue. However, this puts the burden of action on each and every end user to do so for each and every issue, which is non-practical. It should be more logical for the issue responsible to define a specific Distribution List, so that every stakeholder, according to his or her role, would be punctually and automatically informed of relevant progress. Making the notification extensive to specific PERSONS (in their role; but not for all users of a same, generic role) for each specific ISSUE.
Matthew Hesse 4/16/2010 10:33:26 AM
I have some stubborn users who don't want to use BUGtrack and so turn off emails in their Prefs. I occasionally have to go in and turn them back on. If they really want to ignore BUGtrack emails, they can set up an email rule to dump them in Trash or some other folder in which they never plan to look. But at least I'd like to be able to say with 100% assurance that I *know* they were notified.
Feedback
 
Back to Search Results