-
-
Notifications
You must be signed in to change notification settings - Fork 131
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
Fix Provided: Get-JiraUser function inside Invoke-JiraIssueTransition function can return an array of users #349
Comments
Could you please submit a pull request to this issue? |
I'm not familiar with pull requests but I'll look it up and try to figure out what I need to do. |
Thank you, @mirrorgleam . of course I would gladly support you with it :-) |
Just submitted it. I hope it's up to standards. |
And on further review I now see that isn't necessary. |
I do not see your PR yet. can you post the link to the PR you created? |
I see your commit: By clicking this button, you create the PR: This is what you should get: |
AH THINK I FOUND IT :D |
It looks like it's in your pull requests now |
Description
If JIRA has usernames such as "jsmith", "jsmithy", "jsmith1", "jsmithson" and you are trying to assign the ticket to "jsmith" it will fail because the assignee field needs a string but this function is returning an array of strings.
Steps To Reproduce
Expected behavior
Ticket will be assigned to the user in $userDetails
Possible Solution
My Fix: Modified JiraPS.psm1
line 2964:
if ($assigneeObj = Get-JiraUser -InputObject $Assignee -Credential $Credentials) {
change: added
-Exact
flag toGet-JiraUser
functionIn https://github.com/AtlassianPS/JiraPS/blob/master/JiraPS/Public/Invoke-JiraIssueTransition.ps1
line 112
The text was updated successfully, but these errors were encountered: