On Tue, 2006-03-28 at 15:40 -0500, [EMAIL PROTECTED] wrote: > As I said, I'm a big fan of Roundup's concept of the nosy list. Basically > it's a list of email addresses to be notified about changes to a ticket. > Whenever a user makes any change to a ticket, they are automatically added > to the nosy list. Essentially, if you express a stake in a ticket, you > are automatically notified for the rest of that ticket's lifecycle. It's > a simple and intuitive model. If it turns out you don't want to be > notified anymore, you can simply delete yourself fromt he CC list. > > It's been a while, but IIRC Roundup also has ways for adding default > entries in the nosy list as well as making it pretty easy to put hooks > into the workflow to affect the nosy list. > > Roundup's email interface is actually extremely feature-rich (maybe > overkill), handling user registration, ticket submissions, and maybe even > reports (again, hard for me to remember). > > You can see the basic feature list here: > http://roundup.sourceforge.net/doc-1.0/features.html > > Again, it's really the nosy list that's most important.
I would also like to see notification based on reports. i.e., you add your email address to a report, and changes to any ticket that appears in that report get mailed to you as notification. It should aggregate the emails so if the ticket appears in more than one report that you're 'subscribed' to you only get the one notification. Example use cases: 'all' report which matches all tickets in the system for those who want to notified about everything, or a report that shows tickets for your project etc... -- Russ _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
