Opened 15 years ago
Closed 8 years ago
#9007 closed defect (worksforme)
Ticket notification email 'empty' when only CC field changed
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | notification | Version: | 0.11.6 |
Severity: | normal | Keywords: | |
Cc: | Thijs Triemstra | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
If only the CC field of a ticket is changed, a confusing notification is sent. For example:
#8132: Node image 2.10 ---------------------------+------------------------------------------------ Reporter: kamil | Owner: kamil Type: enhancement | Status: new Priority: normal | Milestone: Wishlist Component: Sys - Cluster | Version: N/A Severity: normal | Keywords: Blockedby: | Blocking: 7136, 8130 Due_close: | ---------------------------+------------------------------------------------ -- Ticket URL: <https://www.example.com/ticket/8132#comment:2>
There's no indication of what was changed in the ticket or why the notification was sent. Only once visiting the page for the ticket can you see the reason. eg:
Changed 33 minutes ago by ganesh cc luke, dimitri added; luke dimitri removed
Attachments (0)
Change History (10)
comment:1 by , 15 years ago
Component: | general → notification |
---|---|
Milestone: | → next-minor-0.12.x |
Owner: | set to |
follow-up: 4 comment:2 by , 15 years ago
As a side-note, the specific problem for CC: changes could be avoided altogether if changes to the CC: were not considered to be ticket changes (#9088).
comment:3 by , 14 years ago
Cc: | added |
---|
comment:4 by , 14 years ago
Cc: | added; removed |
---|
comment:5 by , 14 years ago
As efforts to integrate the th:AnnouncerPlugin have stalled lately, I would say it's worth fixing.
comment:6 by , 10 years ago
Milestone: | next-minor-0.12.x → next-stable-1.0.x |
---|
comment:7 by , 10 years ago
Owner: | removed |
---|
comment:8 by , 8 years ago
Milestone: | next-stable-1.0.x → next-stable-1.2.x |
---|
Moved ticket assigned to next-stable-1.0.x since maintenance of 1.0.x is coming to a close. Please move the ticket back if it's critical to fix on 1.0.x.
comment:9 by , 8 years ago
Is this still the case? Seems to me this works (both for CC and for summary mentioned in comment:1), but I'm not sure what the problem was or where it was fixed.
comment:10 by , 8 years ago
Milestone: | next-stable-1.2.x |
---|---|
Resolution: | → worksforme |
Status: | new → closed |
Works for me as well with 1.2-stable.
Same goes for a summary change, I noticed.