Cannot use API to set values for ticket fields if it is drop down menu
Data ultimo post: 09 giu 2022
When we use API to update the ticket fields, we cannot update the fields when the fields are dropdown menu (selected from a list of pre-defined values)
If the field is free text, then we can use the API to update the value.
May I check if this is intended? is it possible to update the ticket fields using API if they are dropdown menu?
0
15
15 commenti
Cheryl Hoskins
I am having a similar problem using `/api/v2/tickets/create_many` endpoint. I tried using the format Erica suggests above and it still didn't work. I found that if I use the associated tag rather than the custom field, it creates the ticket as expected. Should I expect to have to use the tag rather than the custom field when using `/api/v2/tickets/create_many` endpoint?
0
Christopher Kennedy
Erica's comment breaks down the API endpoint you'd need to use to update an individual ticket's custom field value. Are you running into an issue?
0
Frank Burke
Hello,
I don't agree with your point that doesn't use API to set values for ticket fields if it is a drop-down menu. can you please explain to me why we don't use API????
0
Erica Girges
When trying to update a custom dropdown ticket field value, your request body should look similar to this:
Hope this helps!
Erica
0
Holger Hansson
I have the same issue I believe.
--> should update the field as far as I understand. But it does not.
The ticket field json has this metadata (names replaced):
0
Accedi per lasciare un commento.