-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
Error "Get-TfsWorkItem : Value cannot be null. Parameter name: values" when specifying -Fields '*' #211
Comments
I have the same issue, seems that wildcard is not work correctly or i m using it in a wrong way. I obtain alwasy: Get-TfsWorkItem: Value cannot be null. (Parameter 'values') |
igoravl
added a commit
that referenced
this issue
May 15, 2024
…alues" when specifying -Fields '*' #211
igoravl
added a commit
that referenced
this issue
May 15, 2024
…sRestApi, New-TfsTeam and Set-TfsTeam. (#214) * Update VS Code settings * fix: Improve handling of response when content-type is missing * chore: Improve readability * fix: Deal with team projects with reserved regex chars * fix: Issue "Get-TfsWorkItem : Value cannot be null. Parameter name: values" when specifying -Fields '*' #211 * fix: Handling of node paths in Get-TfsWorkItem * Update release notes * Update release notes * Update release notes * chore: Update CodeQL action to v3 * Add SECURITY.md * chore: Update SECURITY.md * fix: Adjust syntax for building in PS Core * chore: Update tests * fix: Wildcard handling * chore: Update security report link * chore: Upgrade WiX to v5 * fix: Correct variable name * fix: Typo * chore: Simplify WiX code * chore: Update release notes
Fixed in #214. Release available at https://github.com/igoravl/TfsCmdlets/releases/tag/v2.6.1%2B3491.1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Get-TfsWorkItem -AreaPath $areaPath -WorkItemType "User Story" -Fields "*"
Get-TfsWorkItem : Value cannot be null.
Parameter name: values
At line:1 char:1
Originally posted by @sbrassard in #183 (comment)
The text was updated successfully, but these errors were encountered: