Skip to main content

Team Foundation Server 2012: Customize the quick add panel

On the TFS 2012 Product Backlog page on the Web Access, you’ll find the quick add panel, a fast and easy way to add new work items to your product backlog. By default, you can only specify a Title field but it is possible to customize it and add more fields.

image

Here are the required steps to customize the panel:

  • Open a command line console and navigate to the Visual Studio Common7\IDE folder(or open a Developer Command prompt for VS2012).
  • Call the Witadmin tool with the exportagileprocessconfig option to export the agile process configuration file.

witadmin exportagileprocessconfig /collection:http://tfsserver:8080/tfs/defaultcollection /p:ProjectName /f:c:\agileconfig.xml

  • Open the exported xml file and locate the AddPanel element.

image

  • Add a field element that specifies the reference name of the TFS field that you want to add to the panel.

image

  • Save the file
  • Call the Witadmin tool again but this time with the importagileprocessconfig option to import the updated configuration file.

witadmin importagileprocessconfig /collection:http://tfsserver:8080/tfs/defaultcollection /p:ProjectName /f:c:\agileconfig.xml

  • That’s it!

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         ...

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.

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’: ...