{ "update": {
"field1": [ {"verb": value}, {"verb": value}, ...],
"field2": [ {"verb": value}, {"verb": value}, ...],
}}
{ "update": {
"fixVersions": [ {"add": "AB 2022.02.000"}]
}}
curl -D- -u ${ADMIN_USER}:${ADMIN_PASSWORD} -X PUT --data "{\"update\" : { \"fixVersions\" : [{\"add\":\"AB 2022.02.00\"}]}}" -H "Content-Type: application/json" https://jira2.company.com/rest/api/2/issue/ProjCode-12345
curl -D- -u ${ADMIN_USER}:${ADMIN_PASSWORD} -X PUT --data "{\"update\" : { \"fixVersions\" : {\"add\":{\"name\":\"AB 2022.02.000\"}}}}" -H "Content-Type: application/json" https://jira2.company.com/rest/api/2/issue/ProjCode-12345
curl -D- -u ${ADMIN_USER}:${ADMIN_PASSWORD} -X PUT --data "{\"update\" : { \"fixVersions\" : {\"add\":[{\"name\":\"AB 2022.02.000\"}]}}}" -H "Content-Type: application/json" https://jira2.company.com/rest/api/2/issue/ProjCode-12345
curl -D- -u ${ADMIN_USER}:${ADMIN_PASSWORD} -X PUT --data "{\"update\" : { \"fixVersions\" : [{\"add\":[{\"name\":\"AB 2022.02.000\"}]}]}}" -H "Content-Type: application/json" https://jira2.company.com/rest/api/2/issue/ProjCode-12345
curl -D- -u ${ADMIN_USER}:${ADMIN_PASSWORD} -X PUT --data "{\"update\" : { \"fixVersions\" : [{\"add\":{\"name\":\"AB 2022.02.000\"}}]}}" -H "Content-Type: application/json" https://jira2.company.com/rest/api/2/issue/ProjCode-12345
first, I would check to see if you can see the field on the issue page as an available field. I have one issue type that doesn't have fixVersions assigned to it, and another that does.
I was getting the same error which led me here.
My final curl command that worked was something like this:
curl --request PUT \
--url 'https://YOURURL.atlassian.net/rest/api/3/issue/ISSUE_ID' \
--user 'USER:APIKEY' \
--header 'Accept: application/json' \
--header 'Content-Type: application/json' \
--data '{
"update": {
"fixVersions": [
{
"add": {"name":"Test Version"}
}
]
}
}'
I was able to adapt this for python to use:
jira.update_issue(issue_key, {'update': {'fixVersions': [{'add': {'name': 'v1.0'}}]}})
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.