Skip to main content

Team Foundation Server 2012: Request feedback remains disabled

For a customer we are experimenting with the Microsoft Feedback Client.

“Microsoft Feedback Client for TFS can help your development team gather both solicited and unsolicited feedback about your software projects from your customers and stakeholders.It allows you to launch an application, capture your interaction with it as video and capture your verbal or type-written comments as well. Your feedback is stored in Visual Studio Team Foundation Server 2012 to support traceability.”

The easiest way to get started is to open the Web Access for a TFS project. On the Home page click on Request feedback under Activities:

image

The Request Feedback form is loaded. Here you can specify the people you want to contact for feedback, some instructions to load the application and some details about the kind of feedback you’re expecting.  After clicking on the Send button, an email is send to the selected people who can download the Feedback client and start using your application.

image

The only problem was that the Send button remained disabled. Bedroefde emoticonI was not the only one with this problem and the solution is simple. What I didn’t notice on the Request Feedback screen is that the yellow fields are required. So just provide a value and the Send button will be available…

image

Labels:

Popular posts from this blog

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

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

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