-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
API: PATCH /hardware/:id - setting requestable field has no effect #6921
Comments
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
This issue has been automatically closed because it has not had recent activity. If you believe this is still an issue, please confirm that this issue is still happening in the most recent version of Snipe-IT and reply to this thread to re-open it. |
This issue has been automatically closed because it has not had recent activity. If you believe this is still an issue, please confirm that this issue is still happening in the most recent version of Snipe-IT and reply to this thread to re-open it. |
I came into same issue.
|
Please confirm you have done the following before posting your bug report:
Describe the bug
Setting the 'requestable' flag for an asset via PATCH to the
/hardware/:id
endpoint has no effect.To Reproduce
Send a PATCH request with
requestable=true
to the/hardware/:id
endpoint, supplying a valid ID of an asset that has the requestable flag not set.I've also tried
requestable=True
,requestable=1
, both yield the same result.Expected behavior
The asset should have the requestable flag set.
Server (please complete the following information):
Error Messages
None, the request ist successfull
{'status': 'success', 'payload': {...}, 'messages': 'Asset updated successfully.'}
The text was updated successfully, but these errors were encountered: