Hello,
I'm a s/w program manager.
I would like to have TFS send mail alerts to team members when I create a new task for them. I would also like to have TFS send a mail to me when they mark a task complete.
None of the out of box alerts seem to fit this bill. Is this possible to set up, if so how?
Many thanks,
Jon
Hi Jon
The team members should register for the project alerts. If you check the first one "My Work items are changed by others" alert then you will receive emails when someone assigns a WorkItem to you. If your team meber subscribe for the alerts and you create a task for him/her then he/she will get email. One they are done with the task they can resolve and assign it back to you so that you will get the email.
I hope this solves your issue. Please let us know if you need any additional information.
Thanks
Sagar Sura
SDET - Visual Studio Team Foundation
That's excellent! I'll try it out.
In the project alerts dialog, can I just enter a group, such as developers@mycorp.com so everyone in that group will receive changed items?
Or do individual developers need to enter their own email addys individually?
Best Regards,
Jon
It is based on the requirement. Forexample if you create a new task and all devs must know about this irrespective of the owner then you can use the group mail id. With this others don't need to subscribe.
If only the assigned dev need to know about this then individual users must subscribe.
Thanks
Sagar
i am currently looking for the same thing that bob mentioned, is there a way for that to be done?
Thanks
1) you can define a custom field in the workflow, say MyCompany.Notify (or use the built in AssignedTo field), and set this at every state change. -- then, with the built in notification system (there's a nice tool here, thanks to Naren) you can set a filter that looks for the user's name in the MyCompany.Notify field.
this gets ugly pretty quick, there's a lot of notifications that need to be manually changed for each user. if somebody leaves / joins the team, you have to modify both the template and the notifications. you could use aliases, like DEVELOPERS / ANALYST / PM, but you still run into the same basic problem of mangement of notifications.
2) alternatively, you could hook the workItemChanged event to a web service, and analyze the workItemChanged object for state changes. for instance, you implement some logic that looks for a bug coming from state ACTIVE -> state TEST and iterate though the list of emails that exist (think: windows group) for this particular change. in effect, you're implementing your own notification system.
i'm curious if there are other ways to get this behavior / if it will be improved in v2?
It might also be worth thinking about using the bissubscribe tool for another way of doing this by hooking into the WorkItemChangedEvent and then monitoring certain fields of the work item when it changes.
Check out Buck's post from a while back for more info.
http://blogs.msdn.com/buckh/archive/2006/04/10/event_filtering.aspx
