#1459: Redesign CC field
--------------------------------+-------------------------------------------
Reporter: ludde | Owner: jonas
Type: enhancement | Status: new
Priority: normal | Milestone: 0.12
Component: ticket system | Version: 0.8.1
Severity: normal | Resolution:
Keywords: notification email |
--------------------------------+-------------------------------------------
Changes (by anonymous):
* cc: [EMAIL PROTECTED] [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED] =>
[EMAIL PROTECTED] [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
Comment:
As stated previously, the danger of being removed from the cc-field is
mitigated (as stated in the initial feature request) by the fact that the
removal from the nosy-list/cc-field is notified to all members of the
nosy-list/cc-field including those just being removed.
From reviewing the above discussions and also thinking about my own needs,
and comparing with RoundUp (see #2953 and #2954), it seems that the
cc/nosy method is very appropriate for small (probably closed) teams,
whereas the "interested" proposal is more appropriate for large (and open)
teams.
Would it not be possible to aggregate both proposals by making the
interested checkbox for each user effectively a view onto an internally
stored (cc/nosy) field, which behaves as the nosy list (auto-add reporter,
and owner). Then it can be a matter of configuration as to which view you
show users - the "interested" view or the full field.
--
Ticket URL: <http://projects.edgewall.com/trac/ticket/1459>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets
