Multiple Email Addresses

[anonymous]

How can I put multiple email addresses in the dispatcher field..? If i put comma seperated email addresses, it only takes the last trailing address.. How do i send the same ticket notification to multiple users???

[shubham_chakraborty@…]

Sry, i forgot my email address above!!

[shubham_chakraborty@…]

Hi,

at the moment it is not possible to assign multiple email addresses to a dispatcher field. I wrote this hack for my project at the university and there we have user groups, who have their own group mail address, so this use case wasn't important to me. Maybe your infrastructre is similiar?
Sadly I don't have much free time these days, so I won't be able to develop and integrate such a feature in near future. But if you need it and if you got the time, feel free to contribute. I think it's just a small and easy patch...

Best regards
Alex

OK, but then is there any other plugin or some combination that allows me to send multiple notification to different people or groups when a ticket is created/modified???

[Ryan J Ollos]

Replying to shubham_chakraborty@infosys.com:

OK, but then is there any other plugin or some combination that allows me to send multiple notification to different people or groups when a ticket is created/modified???

The AnnouncerPlugin allows a group to be included in the CC list: AnnouncerPlugin#Groups.

[shubham_chakraborty@…]

Yes, It does have the Grouping functionality, but it is not secured. I mean the user itself opts to recieve such mails...whereas i want certain groups be made as 'developers', 'managers' and mails within these groups cannot be accessed by the other unless admin makes the user a member of both the groups. AM i missing anything in this plugin or doing it incorrectly?

Can any such combination be made since my user base is big, and without grouping it is very tedious to CC it to 50-60 users at a time. Also usermanager plugin isnt grouping the teams, it only inherits the permissions. Although in the "Assign To" box, name of a team/group created via user manager plugin is visible, it serves no purpose since the teams arent available with option of having members.

[Alexander von Bremen-Kühne]

Hey guys,

yes, you are missing a group management feature in this plugin... I checked the UserManagerPlugin and maybe - but only maybe ;) - there is an easy way to solve the problem using that plugin.
I will try to combine my Plugin with the UserManagerPlugin to provide a User-Group Matrix. I'll tell you whether my approaches will have been successful or not. Just be patient for a couple of days...

Best regards
Alex

[Alexander von Bremen-Kühne]

Hey guys,

I have updated TTD to a new Version. It now depends on the UserManagerPlugin and will not longer use a single email address for each team. Instead you can now assign users to teams and TTD will use the user-configured email addresss for its notification. I just tested it a little, but it seems to work quite well. Despite this, if there any bugs, contact me ;)

Best regards Alex

[anonymous]

U plugin is working fine with the functionality but has some problem with the notification. Firstly, it isnt working on my Apache env but is on my Tracd env. Also, its sending notifications only on new tickets, not when ticket is edit even though the team seems to be selected...You might want to test that one!

[Alexander von Bremen-Kühne]

Hey,

as written on the start page, the plugin only sends out notifcations on creation and not on updates. This is because in our team, we needed the team-notification only for the first classification. Later on the ticket is assigned to one of the teammembers and so not the whole team needs to be informed of changes. Well, this of course only our scenario... You may open a new ticket for notifications on changes and I will work on it. For now I'm fine with the solution ;)

I've tested the plugin as well on my local apache2 as with the standalone tracd. It worked fine with both for me.

A common mistake is, that owner and group of the trac-env-dir are set wrong - for apache it has to be www-data (at least on debian systems...) or else trac is not able to write settings (like the TTD-Field) into its config file.

Please check, whether only my plugin does not work (which means, its really a problem of the plugin) or any other plugin does also not work (which would mean, that you have misconfigured trac or apache). And please give me more details on what is not working in the apache version. You may want to turn on Logmessages in {tracenv}/conf/trac.ini by setting log_level to WARNING and check the logfiles for more information.

Best regards
Alex

[shubham_chakraborty@…]

thnx for the clarification. As for the apache version, i got it working by enabling the custom ticket fields in the TRAC ini by manually typing it. This may be because i installed the plugin via "python setup.py bdist_egg" and not by easy_install, which doesnt work in corporate environments due to downloading limitations. so that may be the reason it didnt work.
Anyways, the team notification is working fine, although the point of having edit notifications being sent is that for example, 10 people on a team working on a ticket to solve...if subsequent notifcation arent sent, then unless each and everyone explicitly watches (watchlist plugin) or start working on it (worklog plugin), the ticket status remains unknown to them till the next time he checks on it. So upon closure by another member(with ticket_modify perm ofcourse), the other members could simply be working on an already closed ticket.
If you want , i could open a new ticket or reopen this one!

[Alexander von Bremen-Kühne]

Please open a new ticket. I will work on it and I already have an idea how this could work. But this won't happen in the next two weeks, since I won't be home for that time.

Feel free to hack on your own - it should be quite easy, if you have the source and use setup.py...

You just have to adjust ​0.11/ttd/api.py and replace the Lines saying 'pass' with these two lines:

    mail = SpecialTicketNotifyEmail(self.env)
    mail.notify(ticket)

This should be enough to get the functionallity you want, I think - but it's untested ;) I will work on a little nicer solution using the config file, so you can configure when a mail should be sent via the admin panel. That's why I will not push this idea into the repository yet.

I hope this OK with you?

Best regards
Alex

[shubham_chakraborty@…]

Thnx a lot! :)