-
-
Notifications
You must be signed in to change notification settings - Fork 130
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #509 from jschlackman/issue-508
Fixed example and improved documentation on `-Properties` hashtable for `Set-JiraUser`
- Loading branch information
Showing
1 changed file
with
3 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -48,7 +48,7 @@ The original value is overridden. | |
### EXAMPLE 2 | ||
|
||
```powershell | ||
Set-JiraUser -User user2 -Properties @{EmailAddress='[email protected]';DisplayName='User 2'} | ||
Set-JiraUser -User user2 -Property @{emailAddress='[email protected]';displayName='User 2'} | ||
``` | ||
|
||
This example modifies a user's properties using a hashtable. | ||
|
@@ -124,6 +124,8 @@ Accept wildcard characters: False | |
Hashtable (dictionary) of additional information to set. | ||
Property names defined in the hashtable are strictly case-sensitive and must match the exact format defined in the [JIRA API schema](https://docs.atlassian.com/software/jira/docs/api/REST/latest/#api/2/user-updateUser), which typically uses camel case. For example, "name" and "displayName" will work correctly when passed in the hashtable but "Name" and "DisplayName" do not. | ||
```yaml | ||
Type: Hashtable | ||
Parameter Sets: ByHashtable | ||
|