Updating Issue Custom Fields

I have adjusted the POST statement as follows and do not get a better response:

curl -X POST \

'https://youtrack.allpack.local/api/issues/APE-102?fields=summary,description,comments,fields(id,name,value)' \

-H 'Accept: application/json' \

-H 'Authorization: Bearer perm:XXXX' \

-H 'Content-Type: application/json' \

-d '{"fields":{"name":"jobid","$type":"SimpleIssueCustomField","value":"1234"}}'

The server returns the following response:

{
"summary": "This changed",
"comments": [
{
"$type": "jetbrains.charisma.persistent.IssueComment"
}
],
"description": "Issue changes",
"fields": [
{
"value": null,
"id": "114-16",
"$type": "jetbrains.charisma.customfields.simple.common.SimpleIssueCustomField"
},
{
"value": {
"$type": "jetbrains.charisma.customfields.complex.enumeration.EnumBundleElement"
},
"id": "91-100",
"$type": "jetbrains.charisma.customfields.complex.enumeration.SingleEnumIssueCustomField"
},
{
"value": {
"$type": "jetbrains.charisma.customfields.complex.enumeration.EnumBundleElement"
},
"id": "91-99",
"$type": "jetbrains.charisma.customfields.complex.enumeration.SingleEnumIssueCustomField"
},
{
"value": {
"$type": "jetbrains.charisma.customfields.complex.enumeration.EnumBundleElement"
},
"id": "91-78",
"$type": "jetbrains.charisma.customfields.complex.enumeration.SingleEnumIssueCustomField"
},
{
"value": {
"$type": "jetbrains.charisma.customfields.complex.state.StateBundleElement"
},
"id": "91-80",
"$type": "jetbrains.charisma.customfields.complex.state.StateIssueCustomField"
},
{
"value": null,
"id": "93-10",
"$type": "jetbrains.charisma.customfields.complex.user.SingleUserIssueCustomField"
},
{
"value": null,
"id": "91-77",
"$type": "jetbrains.charisma.customfields.complex.ownedField.SingleOwnedIssueCustomField"
}
],
"$type": "jetbrains.charisma.persistent.Issue"
}

I have continued to work on this issue but haven't found a solution.

Basically, I copied your suggested code submitting the following:

{"customFields":[{"value":1234, "id":"114-16", "$type":"SimpleIssueCustomField"}]}

The response was the following:

{

"fields": [
{
"value": null,
"id": "114-16",
"$type": "jetbrains.charisma.customfields.simple.common.SimpleIssueCustomField"
}

}

The value is not updating with this process.

Do I have the initial post statement incorrect?

https://youtrack.allpack.local/api/issues/APE-102?fields=summary,description,comments,fields(id,name,value)

Hi Michael, which YouTrack version are you using? Are you willing to upgrade your installation if your license allows updates?

What are the settings of the `jobid` custom field, could you please share a screenshot?

We are currently running 2018.3. Yes, we are willing to upgrade if the license allows it. Here is a screenshot of the jobid settings:

Michael, I'm sorry for the late response.

I believe the problem lies in the $type names and the YouTrack version you're using. In the older versions of YouTrack (2018.3 and older), the $type names were longer, so they were shortened in the later versions. See the "SimpleIssueCustomField" in my examples and the "jetbrains.charisma.customfields.simple.common.SimpleIssueCustomField" in yours.

Also, the "fields" attribute" was renamed to "customFields".

There are two options:

1) You can use the longer $type name, i.e., use this for the body: 

{"fields":[{"value":1234, "id":"114-16", "$type":"jetbrains.charisma.customfields.simple.common.SimpleIssueCustomField"}]}

2) You can upgrade your YouTrack to version 2019.x (and then to the 2020.x if you wish, but that's not necessary for your goals) and use the examples I've provided earlier.

I hope this helps, please let me know how it goes.