Re: understand how to control who gets the mails

Thanks Ralf,

the hint, that the auditor is called again if I set something in the 
reactor is really important. (but I did not do that right now)
I figured out my problem after debugging the whole nosymessage()
I had no permission to view msg.content as I do not allow to view other 
users items.
I now added the permission for the msg.content so the good_recipient 
does not fail on the users.

Everything working now regarding this issue.

thanks,
Martin


Am 03.07.2015 um 09:41 schrieb Ralf Schlatterbeck:
> On Thu, Jul 02, 2015 at 09:17:45PM +0200, Martin Thomas Swaton wrote:
>> Hi guys,
>>
>> after digging into roundup for some days now I was able to create some
>> auditors and reactors e.g. autoassign on reply of a support member or
>> prevent status change if the creator submits a second mail that is still
>> unread and so on.
>>
>> But what I am not able to realice is, to control the recipients of new /
>> commented issues.
>>
>> I can add users to the newvalues['nosy'] or oldvalues['nosy'] (for
>> reactor) but they won't be mailed. And I do not really understand why.
>> Maybe because they already are on the recipients list of that msgid -
>> but I do not understand why, when they did not get this message yet and
>> only got the original msg of this issue.
>>
>> I also tried to set the recipients new, but that did not work as I
>> supposed it to be done.
>>
>> So maybe someone could help me to understand how this notification
>> system works and where I can manipulate who is mailed.
>>
>> e.g. I want to inform the creator when the status changes and otherwise
>> prevent to mail the creator.
>>
>> I did everything within nosyreactor detector script.
> You need to modify the nosy list in an auditor not in a reactor.
> Modifying oldvalues has no effect. The auditor runs pre-commit (before
> the commit to the database) while all reactors run post-commit. So you
> can't change the values in a reactor. (In fact you could by calling
> cl.set in a reactor but this would again call the auditor for that
> change and in turn the reactor and you can easily run into a recursive
> loop there, so it's not recommended to change anything in a reactor)
>
> If you *did* add users in an auditor (you mention newvalues) we would
> need your code to check why it's not working.
>
> Ralf
>


------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/