Opened 6 years ago
Last modified 7 months ago
#12997 new defect
Sending email on ticket attachments with "Replace existing attachment of the same name"
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | next-stable-1.6.x |
| Component: | notification | Version: | |
| Severity: | normal | Keywords: | attachment |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
When a file is attached to a ticket and "Replace existing attachment of the same name" is choses, two emails are sent: *) The first email contains "Attachment "zzz.patch" removed and has as subject "[Project #id] {Current summary} (was: {former summary})". *) The second email contains "Attachment "zzz.patch" added and has as subject "[Project #id] {Current summary}"
Including a summary the ticket has in the past is not necessary and clutters the email. The email on uploading an attachment shall contain only the current summary, except the very same operation changes the summary.
I would like to get on the operation "replacing existing attachment" a single email.
https://code.djangoproject.com/ticket/ uses track and for these changes and I was told to report them here (https://code.djangoproject.com/ticket/29240)
Attachments (0)
Change History (4)
comment:1 by , 6 years ago
comment:2 by , 6 years ago
| Keywords: | attachment added |
|---|---|
| Milestone: | → next-stable-1.2.x |
comment:3 by , 4 years ago
| Milestone: | next-stable-1.2.x → next-stable-1.4.x |
|---|
Replying to dpa-bugs@…:
Your report seems to mixup two issues, but the ticket you opened with the Django project is more clear. The (was: {former summary}) may be seen when changing the summary, but should not be seen when replacing an attachment.
I've considered previously that it might be good to move the summary change to notification body and just use the new summary in the subject. However, it needs to be debated.
Agreed, that should get fixed.