Closed jschlackman closed 3 weeks ago
Update: this appears to actually be a documentation issue. I realized after revisiting my workaround that passing @{Name="csmith"}
in the -Property
parameter will fail but @{name="csmith"}
succeeds. It appears the user property names passed to the API are case sensitive (which is not specified in the official REST API docs) and do not match the capitalization used in the JiraPS outout objects or the example code given in the JiraPS documentation.
Description
When using the
Set-JiraUser
cmdlet with the-Property
parameter to set properties not named in the cmdlet (e.g. updating the user's login name), the command fails with the following output:Steps To Reproduce
Set-JiraConfigServer
andNew-JiraSession
as per normalExpected behavior
Username for user bsmith should be changed to csmith
Workaround
In the same environment, crafting the REST body manually and calling
Invoke-JiraMethod
with the correct Uri per the below example produces the expected behavior:(Note: URL of Jira server has been changed for privacy)
Your Environment
Jira Server Version: 9.12.2