I am currently working to build a REST API that will create a service desk request, but the information form the Insight documentation indicates that the object Key must be used. so, my dumb question is...."How do we do that when the user needs to select the object be name from a drop down list on the request?"
{
"fields": {
"project":
{
"key": "TEST"
},
"summary": "REST ye merry gentlemen.",
"description": "Creating of an issue using project keys and issue type names using the REST API",
"issuetype": {
"name": "Task"
},
"customfield_10100" : [{"key" : "TEST-1"}],
"customfield_10200" : [{"key" : "TEST-1"}, {"key" : "TEST-2"}]
}
}
Our goal is to create requests via API, but the user will need to make the selections, so if that is the case, then using the key as a parameter will not work.
Am I missing something? Are we going to have to make a call to the database to pull the data first, then insert the key value?
Any help is greatly appreciated.
Hi Thomas,
Yes the value stored for the custom field is the Key. Depending on how you get the name, it seems reasonable that you also should get the Key at the same time if you are our REST API.
Normally, you could set one value for a dropdown, what is displayed, and one value which is used, like the example from https://www.w3schools.com/tags/tag_select.asp
That way the user can see the objects label, but what is used when storing is the Key.
Cheers!
Alexander
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.