Opened 12 years ago
Last modified 6 months ago
#11943 new enhancement
Ticket delete notifications
| Reported by: | Ryan J Ollos | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | next-major-releases |
| Component: | notification | Version: | |
| Severity: | normal | Keywords: | ticket delete |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Trac supports ticket deletion through the ticket remove TracAdmin command, and the TicketDeleter Component in /tracopt/ticket. It would be useful to receive notifications when tickets are deleted.
The AccountManagerPlugin has a similar feature of sending notifications when users are removed. The subject and body are very simple, e.g. Deleted User: tonyjha99. The users to receive notifications are configured through the [account-manager] account_changes_notify_address option.
Attachments (0)
Change History (6)
comment:1 by , 9 years ago
follow-up: 3 comment:2 by , 6 months ago
Does this persist in Trac 1.6? If so, are you saying that subscribers to a ticket are not notified if that ticket is deleted?
follow-up: 4 comment:3 by , 6 months ago
Replying to Philippe Cloutier <chealer@…>:
Does this persist in Trac 1.6? If so, are you saying that subscribers to a ticket are not notified if that ticket is deleted?
Yes. Please reproduce the issue and/or investigate the code before submitting the comment.
follow-up: 5 comment:4 by , 6 months ago
Greetings Jun,
Replying to Jun Omae:
Replying to Philippe Cloutier <chealer@…>:
Does this persist in Trac 1.6? If so, are you saying that subscribers to a ticket are not notified if that ticket is deleted?
Yes.
Thanks, but you are quoting 2 questions, so it’s unclear which you are answering.
Please reproduce the issue and/or investigate the code before submitting the comment.
What? Which comment?
follow-up: 6 comment:5 by , 6 months ago
Thanks, but you are quoting 2 questions, so it’s unclear which you are answering.
Please reproduce the issue and/or investigate the code before submitting the comment.
What? Which comment?
comment:2. I spent my time to investigate Trac source code about your comment "Does this persist in Trac 1.6? If so, are you saying that subscribers to a ticket are not notified if that ticket is deleted?". If you would actually reproduce and/or investigate it instead of just posting comments, I wouldn't spend my time. This applies to this ticket and other tickets too.
comment:6 by , 6 months ago
Replying to Jun Omae:
Thanks, but you are quoting 2 questions, so it’s unclear which you are answering.
Please reproduce the issue and/or investigate the code before submitting the comment.
What? Which comment?
In that case, it would have been much clearer to write "your comment", but regardless, I cannot make sense of comment:3. You asked to do something before an event which had already happened. That is impossible.
I spent my time to investigate Trac source code about your comment "Does this persist in Trac 1.6? If so, are you saying that subscribers to a ticket are not notified if that ticket is deleted?". If you would actually reproduce and/or investigate it instead of just posting comments, I wouldn't spend my time.
Nobody asked anyone to do that. comment:2 was asking the submitter whether the issue remained relevant, in order to prevent me (or others) from wasting time figuring out what this report means or investigating a problem which does not even specify an affected version. In other words, it asks Ryan whether the issue persists once the affected instance is up-to-date.
This comment is from Philippe "Chealer" Cloutier. All of my comments and contributions in this ticket are offered under the terms of CC0 1.0 (unless otherwise noted).
#12695 was closed as duplicate.