Modify ↓
Opened 19 years ago
Closed 19 years ago
#1639 closed defect (duplicate)
CC handling not scalable
| Reported by: | Owned by: | Jonas Borgström | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | ticket system | Version: | 0.8.1 |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
The handling of the CC field is not scalable for large communities. Imagine a bug report with 50 CC entries and now imagine a user seeing trac the first time. He could remove all CC entries with one little mistake.
It would be better if there would be an "add cc" field (like Bugzilla has) and a separate list for removing CC entries.
I also think that the template will containe a lot of clutter if the complete content of the CC field is repeated multpile times in the change list (CC changed from … to …). Might be a lot overhead and scolling for CC lists with 10, 20, 50 or 100 users.
Attachments (0)
Note:
See TracTickets
for help on using tickets.
This is basically covered by #1459.