Skip to content
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

No returned payload when using Set-FreshServiceTicket -id x -workspace_id x #10

Open
rasimmers opened this issue Oct 12, 2023 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@rasimmers
Copy link
Contributor

Expected Behavior

When Set-FreshserviceTicket -id x -workspace_id x is executed, the modified ticket will be returned from Set-FreshserviceTicket.

Current Behavior

Using the https://api.freshservice.com/#move_a_ticket method, the documentation indicates the response will have a wrapper of "ticket{}". When the payload is returned, there is no ticket wrapper and the parse fails returning a null response from Set-FreshserviceTicket. Validated Change, Release, Problem methods properly return wrapper.

Possible Solution

Reported to Freshworks as bug and awaiting remediation. Temporary solution implemented in function to return $result.Content when workspace_id is used versus $result.Content.Ticket. Once the bug has been corrected, the function will be updated to remove the workaround.

@rasimmers rasimmers added the bug Something isn't working label Oct 12, 2023
@rasimmers rasimmers self-assigned this Oct 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant