Edgewall Software
Modify

Ticket #8607 (new enhancement)

Opened 2 years ago

Last modified 5 months ago

Option to skip notification to subscribers when a ticket is updated

Reported by: Ryan Ollos <ryano@…> Owned by: eblot
Priority: normal Milestone: next-major-0.1X
Component: notification Version: 0.11.5
Severity: normal Keywords: minoredit
Cc: sebastian@…, keshav.kini@…, bebugz@…
Release Notes:
API Changes:

Description

Consider the following scenarios for editing a ticket:

  1. Changing a minor typo in the ticket Description
  2. Adding some entries to the Keywords field
  3. Changing the Milestone, Component, Type, etc ...
  4. Adding an attachment, when the attachment was mentioned in the previous message, therefore all users can expect it will be posted to the ticket within minutes and don't need to see another email telling them an attachment was added.

Users on my team receive a lot of email from Trac each day, and it is frustrating and Trac becomes less effective when they receive email notifications when someone is just cleaning up or making some minor changes to a ticket.

Rather than setting up a lot of options in trac.ini that determine who and when a subscriber is notified of changes, I propose that a checkbox is added to the right of Submit Changes. When the Don't Notify Subscribers checkbox is selected, notifications emails are not sent on a ticket update.


The question then arises, what permission should be required for this checkbox to be present. Perhaps someone running a Trac instance does not want users to be able to change a ticket without, for instance, the ticket's owner receiving a notification. I propose two options for the [notification] section of trac.ini.

  1. optional_notify_authenticated = {true, false}
  2. optional_notify_anonymous = {true, false}

Option 1 would show/hide the Don't Notify Subscribers checkbox for authenticated users. Option 2 would show/hide the Don't Notify Subscribers checkbox for anonymous users. Users with TICKET_ADMIN permission would always see the checkbox.

Attachments

SubmitChangesButton.png (3.8 KB) - added by Ryan Ollos <ryano@…> 2 years ago.

Download all attachments as: .zip

Change History

Changed 2 years ago by Ryan Ollos <ryano@…>

comment:1 Changed 2 years ago by Ryan Ollos <ryano@…>

Request-A-Hack on Track-Hacks.org: #5495.

comment:2 Changed 2 years ago by Sebastian Krysmanski <sebastian@…>

  • Cc sebastian@… added

comment:3 Changed 2 years ago by jevans

Alternatively perhaps add TICKET_CLEANUP and WIKI_CLEANUP permissions (or some such) to control access to the option. Personally I'd only allow it for minor text edits - I'd want notification of property changes. But yes, there have been times I haven't made minor corrections to avoid sending notification. Sounds like a great hack.

comment:4 Changed 2 years ago by cboos

  • Component changed from ticket system to notification
  • Keywords minoredit added
  • Milestone set to next-major-0.1X
  • Owner set to eblot

Sounds interesting, and in line with the discussion in #7758.

But if I may, we are more in need of an active maintainer for the notification subsystem than yet another tweak ;-)

comment:5 Changed 17 months ago by cboos

#5332 was closed as a duplicate of this ticket.

comment:6 Changed 6 months ago by keshav.kini@…

  • Cc keshav.kini@… added

comment:7 Changed 5 months ago by bebugz@…

  • Cc bebugz@… added

comment:8 Changed 5 months ago by bebugz@…

For these impatient like me wouldn't that be a quick-n-dirty solution to make custom boolean field on ticket (trac.ini) and hardcode/patch the notification to analyse of this field to completely off the notification. As the proposal prior to proper longterm solution.

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as new
as The resolution will be set. Next status will be 'closed'
to The owner will be changed from eblot. Next status will be 'new'
The owner will be changed from eblot to anonymous. Next status will be 'assigned'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.