Skip to main content

Team Foundation Server 2012/Service: Create events from web access for other user

I always enjoy browsing through Team Foundation Service, the cloud version of  TFS.  Every day I discover new functionality and features.

Last week I noticed that administrators are able to create team alerts for other users. You could already do this by using the Alerts Explorer from the TFS Power Tools but then those alerts are actually owned by the person creating them and not able to be managed, edited, or disabled for the person they are intended. Afterwards I went back to our on premise TFS environment to notice that the same functionality was also available there… Glimlach

To use this feature:

  • Open the Team Foundation Server web access
  • Browse to a specific Team Project
  • Click on the configuration icon in the right corner to go the configuration section

image

  • On the Overview page click on a Team name:

image

  • On the Team configuration page, click on alerts

image

  • In the Administrator actions on the left, you can search for another user

image

  • After selecting a user, you can manage his events on the right

image

More information here: http://www.edsquared.com/2012/02/09/Creating+EMail+Alerts+For+Team+Members+In+TFS.aspx

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more