Setting 'responsibility' to none with the REST API

 
Author
Message
SysAider
3
 
Hi,
I need to use the rest api to create service requests that are assigned to a specific group (assigned_group) but not assigned to a user.

I manage to assign a specific user by using the 'responsibility' field in the json body, but I don't know how to set it to no user.

I tried to set it with no value at all, with "none" as a value and with "null" as a value but it doesn't work.

SysAider
3
 
anybody?
SysAid Community Manager Product Team
4492
 
Hi orik,

I've checked this with the team - the "assigned to" field can't be none when creating SR through the API.
If the field is populated from a template, if the template's "assigned to" is empty it's assigned to the logged in user.

I guess I can submit this as a feature request if you'd like.

Cheers,
Danny

This message was edited 1 time. Last update was at Oct. 24, 2017 09:10 AM

SysAid Community Manager Product Team
4492
 
Correction: You can actually add this to the request body
{
"key":"responsibility",
"value":"0"
}

Note: while in admin-side, you might still see the ticket as assigned to the logged-in user, but the ticket will not actually be assigned to any admin until Apply is pressed (you can check this in EUP/SSP - the ticket is not assigned).

Cheers,
Danny
SysAider
3
 
Thanks Danny,
I need it only for "admin-side" use.
I tried to set it to "0" but it still being assigned to the api user and apply is already pressed. (What is EUP/SSP?)

You said the field is populated from a template, is there any way to edit this template or use another one?
If not, I'd be glad if you submit it as a feature request.

This message was edited 1 time. Last update was at Oct. 24, 2017 08:48 AM

SysAid Community Manager Product Team
4492
 
Sorry, I missed an "if" in that sentence If the field is populated from a template.

EUP = End-User Portal, SSP = Self-Service Portal. While visually you see the SR as being assigned to the logged in user, it is actually not assigned to anyone, as can be checked in the database or in EUP/SSP as described. We have now opened a bug for this behavior - I will update here once there is a bug number

Thanks,
Danny