Roundup Tracker - Issues

Message5535

Author pefu
Recipients Ivan Pozdeev, pefu
Date 2016-04-19.05:24:57
Message-id <1461043498.43.0.876136821616.issue2550906@psf.upfronthosting.co.za>
In-reply-to
I just had a closer look and discovered that the option
"messages_to_author" is set to "yes" at least in the "devel", "jinja2"
and "responsive" templates shipped with Roundup.  

A per user option wouldn't be so hard to implement:  The code 
dealing with this is located in roundup/roundupdb.py method
nosymessage() at line 312.  It currently reads::

     # possibly send the message to the author, as long as they aren't
     # anonymous
     if (good_recipient(authid) and
         (self.db.config.MESSAGES_TO_AUTHOR == 'yes' or
          (self.db.config.MESSAGES_TO_AUTHOR == 'new' and not oldvalues) or
          (self.db.config.MESSAGES_TO_AUTHOR == 'nosy' and authid in
          self.get(issueid, whichnosy)))):
        add_recipient(authid, sendto)

It would be possible here to check whether the user class of the db
instance in question has an additional boolean attribute 
(we have to select a name for it) and test this instead of the global
flag self.db.config.MESSAGES_TO_AUTHOR 

There are some tests in test/test_mailgw.py which must to be modified
also, if this is going to implemented by someone.

Best Regards, Peter Funk.
History
Date User Action Args
2016-04-19 05:24:58pefusetmessageid: <1461043498.43.0.876136821616.issue2550906@psf.upfronthosting.co.za>
2016-04-19 05:24:58pefusetrecipients: + pefu, Ivan Pozdeev
2016-04-19 05:24:58pefulinkissue2550906 messages
2016-04-19 05:24:57pefucreate