Skip to content

Releases: igoravl/TfsCmdlets

Release 2.8.1+3553.1

16 Jul 15:08
ca2d168
Compare
Choose a tag to compare

This release fixes an issue with the New-TfsUser cmdlet.

Fixes

  • Fixed an issue where the New-TfsUser cmdlet could throw an error when not supplying project entitlements via the -Project argument.

Release 2.8.0+3546.2

09 Jul 06:58
645b1fd
Compare
Choose a tag to compare

This release adds two new cmdlets: New-TfsUser and Remove-TfsUser.

New cmdlets

  • New-TfsUser: Creates a new user in the organization and optionally adds them to projects.
  • Remove-TfsUser: Removes a user from the organization.

Release 2.7.1+3540.1

03 Jul 19:27
4e35fb0
Compare
Choose a tag to compare

This release fixes an issue with the Chocolatey publishing process. No changes have been made to the cmdlets.

Release 2.7.0+3540.2

03 Jul 17:46
e570b7d
Compare
Choose a tag to compare

This release adds support for suppressing notifications when creating or updating work items.

New features

  • Adds -SuppressNotifications switch to New-TfsWorkItem and Set-TfsWorkItem to suppress notifications when creating or updating work items. This is useful when you are creating or updating a large number of work items and don't want to flood the notification feed of team members.

Release 2.6.1+3491.1

15 May 16:10
a8ad84b
Compare
Choose a tag to compare

Ouch! It's been a while since the last release! Sometimes life gets in the way, but I'm back!

This release fixes bugs in Get-TfsWorkItem, Get-TfsArea, Get-TfsIteration, Invoke-TfsRestApi, New-TfsTeam and Set-TfsTeam.

Fixes

  • Fixes #211, where Get-TfsWorkItem would throw an error when the -Fields parameter was "*".
  • Fixes a bug in Invoke-TfsRestApi where Azure DevOps APIs whose responses were missing the content-type header would throw an error.
  • Fixes a bug in Get-TfsArea and Get-TfsIteration where team projects containing Regex-reserved characters (such as parentheses) would throw an error. This bug would indirectly affect New-TfsTeam and Set-TfsTeam due to their reliance on the same underlying class to handle area and iteration paths when creating/updating teams.
  • Fixes a bug in Get-TfsWorkItem where the -AreaPath and -IterationPath parameters would not work when the specified path either started with a backslash or did not contain the team project name.
  • Adds the installed module version to the Azure DevOps Shell startup command to prevent loading an older version of the module when the PSModulePath variable contains an older version of the module listed earlier in the search path.

Release 2.6.0+2898.5

01 Oct 00:10
276cfc9
Compare
Choose a tag to compare

This release fixes a bug in Get-TfsWorkItemQuery and Get-TfsWorkItemQueryFolder, and adds two new cmdlets.

New cmdlets

  • Undo-TfsWorkItemQueryRemoval and Undo-TfsWorkItemQueryFolderRemoval allow you to undo the deletion of a query or query folder. This is useful when you accidentally delete a query or query folder and want to restore it.

To restore a deleted query:

# You can either pipe the deleted query from Get-TfsWorkItemQuery to Undo-TfsWorkItemQueryRemoval...
Get-TfsWorkItemQuery 'My Deleted Query' -Scope Personal -Deleted | Undo-TfsWorkItemQueryRemoval

# ... or you can specify the query directly when calling Undo-TfsWorkItemQueryRemoval
Undo-TfsWorkItemQueryRemoval 'My Deleted Query' -Scope Personal

The same applies to query folders - with the distinction that folder can be restored recursively by specifying the -Recursive switch. When -Recursive is omitted, only the folder itself is restored, without any of its contents. You can then restore its contents by issuing further calls to Undo-TfsWorkItemQueryRemoval and/or Undo-TfsWorkItemQueryFolderRemoval.

# You can either pipe the deleted folder from Get-TfsWorkItemQueryFolder to Undo-TfsWorkItemQueryFolderRemoval...
Get-TfsWorkItemQueryFolder 'My Deleted Folder' -Scope Personal -Deleted | Undo-TfsWorkItemQueryRemoval -Recursive

# ... or you can specify the folder directly when calling Undo-TfsWorkItemQueryFolderRemoval
Undo-TfsWorkItemQueryFolderRemoval 'My Deleted Folder' -Scope Personal -Recursive

Fixes

  • Fixes a bug in Get-TfsWorkItemQuery and Get-TfsWorkItemQueryFolder where the -Deleted switch was not respected and deleted items would not be returned.

Release 2.5.1+2859.4

22 Aug 05:28
4b27681
Compare
Choose a tag to compare

This release fixes a bug in New-TfsWorkItem.

Fixes

  • Fixes #191, where AreaPath and IterationPath arguments are switched.

Release 2.5.0+2840.2

03 Aug 02:34
f91c738
Compare
Choose a tag to compare

This release introduces new cmdlets and fixes a few bugs.

New cmdlets

  • Start-TfsBuild: Starts a pipeline (YAML) / build (Classic).
  • Get-TfsTeamProjectMember: Returns the members of a team project, as shown in the "Members" widget in the team project's Summary page (closes #59).

Fixes

  • Fixes a bug in New-TfsWorkItem and Set-TfsWorkItem where IterationPath was not being set.

Release 2.4.1+2827.1

21 Jul 02:52
86a036e
Compare
Choose a tag to compare

This release fixes bugs and add improvements to New-TfsWorkItem and Set-TfsWorkItem.

Improvements

  • Identity fields in New-TfsWorkItem and Set-TfsWorkItem (such as "Assigned To") now support either email addresses or user display names as valid values. Previously, only user display names were supported.

Fixes

  • Fix "Set-TfsWorkItem fails with {type} to {type}[] (array) conversion error" (#172)
  • Fix a bug in New-TfsWorkItem and Set-TfsWorkItem where changes to the AssignedTo field would not be reflected in the Work Item.

Release 2.4.0+2768.3

23 May 05:11
16b4a4f
Compare
Choose a tag to compare

This release adds support for interactive logons in PowerShell Core (6+) shells.

Improvements

  • All the Connect-* cmdlets now support interactive (-Interactive) logon in PowerShell Core (6+) shells. Previously, only Windows PowerShell (5.*) terminals supported interactive authentication. NOTE: Interactive logons in PowerShell Core require Azure DevOps Services. TFS / Azure DevOps Server remain unsupported for interactive logons in PowerShell Core. To connect to an on-premises server in a PowerShell Core shell, you're still required to use either username/password credentials or a personal access token.
  • Some minor consistency improvements to the way Work Item Query cmdlets Get-TfsWorkItemQuery and Get-TfsWorkItemQueryFolder handle paths. Additionally, Get-TfsWorkItemQueryFolder can now return the "root" folders (My Queries and/or Shared Queries) when specifying / as the folder path. That comes in handy when you want to e.g. use some Security APIs that require the ID of the folders all the way from the beginning of the hierarchy.

Fixes

  • Under certain circumstances, Get-TfsWorkItem would return an invalid ID, due to a change in the response from the WorkItem REST API (fixes #172)
  • Fix a bug in New-TfsWorkItemQuery and New-TfsWorkItemQueryFolder, where queries and folders could not be created when their parent did not exist.