search

ipatalas / vscode-sprint-planner

Plan your sprints in VSCode directly!
MIT License
37 stars 22 forks source link

Iterations Note being Detected #26

Closed cgrisham closed 3 years ago

cgrisham commented 3 years ago

When trying to define my iterations it isn't able to search my tenant for the proper iterations.

Further when trying to push an update so that it uses current iterations I get a 401 error and the following returned in the output

[4:21:57 PM.881] Iteration not specified - will default to @CurrentIteration
[4:21:57 PM.881] Getting current iteration info...
[4:21:57 PM.943] ''

I have manually retrieved the Iteration ID and tried supplying that using IT#47fa6b31-41b4-*****-985d-abdba9e604f0

And still get the same message above.

ipatalas commented 3 years ago

Can you set planner.azure-devops.debug to true and try again? There should be much more verbose logging then, including request and response dump. Hope this will help figuring out what's the issue. If that doesn't help can you make the following request using Postman or some other tool:

GET https://dev.azure.com/<organization>/<project>/_apis/work/teamsettings/iterations?$timeframe=current
Authorization: Basic PAT <your_token>

Let me know what are the results.

401 might mean expired/wrong token but that's only a guess for now.

And one more thing. Is iterations the only thing not working correctly? Can you successfully publish something?

cgrisham commented 3 years ago

Thanks for pointing me in correct direction I was able to resolve the issue. Had my Area and Team parameters in the config switched.