Modify ↓
Opened 18 years ago
Last modified 5 days ago
#7073 new enhancement
Tickets: subscribers of duplicate tickets are not necessarily notified
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | next-major-releases |
| Component: | notification | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description (last modified by )
If ticket A is marked as a duplicate of ticket B, notifications about modifications to either ticket A or B should be sent to subscribers of ticket A and subscribers of ticket B.
Attachments (0)
Change History (3)
comment:1 by , 18 years ago
comment:2 by , 11 years ago
| Owner: | removed |
|---|
comment:3 by , 5 days ago
| Description: | modified (diff) |
|---|---|
| Summary: | notify dup subscribers → Tickets: subscribers of duplicate tickets are not necessarily notified |
I have not reproduced this, but have taken the liberty to revise this ticket’s title and description based on my best guess about what you meant.
Note:
See TracTickets
for help on using tickets.



Well, currently there's no "formal" notion about which ticket was the original one, when a ticket closed as duplicate. As such, this ticket depends on #1395.