Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backlog List not populating when installed in TFS 2017 Update 3.1 #44

Open
JaDevGuy opened this issue Jun 22, 2018 · 4 comments
Open

Backlog List not populating when installed in TFS 2017 Update 3.1 #44

JaDevGuy opened this issue Jun 22, 2018 · 4 comments

Comments

@JaDevGuy
Copy link

Is this extension supported on TFS 2017 Update 3.1? After installing it the backlog dropdown is not being populated.

@louisfischer
Copy link

louisfischer commented Jun 29, 2018

@JaDevGuy We are currently on TFS 2017 Update 3.1 and also are having the same issue. It use to work but now it does not. Attached is a screenshot of the issue. I hope that helps.

image

@shayki5
Copy link

shayki5 commented Jul 2, 2018

Also in our TFS 2017.3 the widget does not show any data (after configure).
This errors on the console:
TypeError: Cannot read property 'EnableAppInsightTelemetry' of undefined
POST http://tfs:8080/tfs/Collection/TP/TP%20Team/_apis/wit/wiql 400 (Bad Request)
TypeError: Cannot read property 'templateName' of undefined
ccess to Script at 'http://tfs:8080/tfs/_apis/public/gallery/publisher/ms-devlabs/extension/RollUpBoard/2.0.35/assetbyname/lib/ldclient.min.js' from origin 'null' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access.

@peckhamm
Copy link

I noticed that when using Internet Explorer I'm not seeing any data. But when I use Chrome, there is a slight delay (about 5 seconds) and then the data shows up. Hope that might add some value.

@louisfischer
Copy link

So it looks like when using the On-Premise version of TFS (Azure DevOps Server), the extension is looking for the [System.Area] in the post to the "_apis/wit/wiql' endpoint.

The below image is just using the Wiql Editor.
image

We recently started using the Team instead of Area according to the ms docs instructions here. Once i changed the WIsql to look for Team, the query succeeded.

image

So the question is, can the extension be modified to use another different field or allow for customization of the WSQL query?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants