Edgewall Software
Modify

Opened 5 years ago

Closed 5 years ago

#11535 closed enhancement (wontfix)

Option to disable notifications on batch modify

Reported by: Ryan J Ollos Owned by: Ryan J Ollos
Priority: normal Milestone:
Component: notification Version:
Severity: normal Keywords: batch-modify
Cc: Branch:
Release Notes:
API Changes:

Description

Even with the pending changes to the notification system, and the ability to control subscriptions, we should consider adding an option on 1.0-stable to disabled notifications on batch modify. This was discussed on the mailing list.

Attachments (0)

Change History (7)

comment:1 by Steffen Hoffmann, 5 years ago

While the test scenario I mention is not a real issue, the common use case for mass editing several, maybe tens of tickets is a real concern. And it would be totally acceptable, if not required to couple the ability for (temporarily) disabling change notifications with a suitable permission (TICKET_ADMIN?).

comment:2 by Ryan J Ollos, 5 years ago

Milestone: next-stable-1.0.x1.0.3

comment:3 by Ryan J Ollos, 5 years ago

Owner: set to Ryan J Ollos
Status: newassigned

comment:4 by Ryan J Ollos, 5 years ago

Milestone: 1.0.31.0.4

comment:5 by Peter Suter, 5 years ago

It may be worth noting that Trac notifications only send one email per batch modify event (unlike the "TagsPlugin mass tag change admin function" described on the mailing list), so I'm not sure I see a need for disabling notifications on batch modify specifically.

(For Trac 1.1.4+ we could look at th:QuietPlugin, or even consider a subscriber that allows configuring rules like Never Notify: Updater was in quiet mode in the notification user preferences.)

in reply to:  5 ; comment:6 by Ryan J Ollos, 5 years ago

Replying to psuter:

It may be worth noting that Trac notifications only send one email per batch modify event (unlike the "TagsPlugin mass tag change admin function" described on the mailing list), so I'm not sure I see a need for disabling notifications on batch modify specifically.

You are right about the change probably not being needed. I was confused about the functionality at the time I created the ticket.

(For Trac 1.1.4+ we could look at th:QuietPlugin, or even consider a subscriber that allows configuring rules like Never Notify: Updater was in quiet mode in the notification user preferences.)

I like the functionality of the QuietPlugin, so having that integrated in the core is appealing.

I'll leave to your judgement whether to move this ticket to a 1.1.x milestone or close it as wontfix, with the possibility that the requested functionality will be added in another ticket.

in reply to:  6 comment:7 by Peter Suter, 5 years ago

Milestone: 1.0.4
Resolution: wontfix
Status: assignedclosed

Replying to rjollos:

Replying to psuter:

It may be worth noting that Trac notifications only send one email per batch modify event (unlike the "TagsPlugin mass tag change admin function" described on the mailing list), so I'm not sure I see a need for disabling notifications on batch modify specifically.

You are right about the change probably not being needed. I was confused about the functionality at the time I created the ticket.

I'll leave to your judgement whether to move this ticket to a 1.1.x milestone or close it as wontfix, with the possibility that the requested functionality will be added in another ticket.

There's already an enhancement request for a feature to skip notifications (#8607), so I'd say we can close this ticket.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Ryan J Ollos.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.