nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to Update Issue status in cloud using REST API

Radhakrishna_Sangishetti

Hi All,

when am try to update issue status using REST API its showing below error

{"errorMessages":[],"errors":{"status":"Field 'status' cannot be set. It is not on the appropriate screen, or unknown."}}\

my request json is:

{
" update " : {
" comment " : [{
" add " : {
" body " : " Status Change to Done "
}
}
]
},
"fields" : {
"status" : {
"name" : "Done",
"id" : "10001"
}
}
}

please can anyone help me on this issue.

Accepted answers

All comments

Petar Petrov _Appfire_

You can not change the status as a field - you must transition the issue - see the REST Endpoint documentation for:

POST /rest/api/2/issue/{issueIdOrKey}/transitions

Nic Brough -Adaptavist-

Status is not a "field", it's an indicator of position in the workflow. You have to use transitions to change the status.

For REST, see the REST Endpoint documentation

Nic Brough -Adaptavist-

Oops. Sorry, Petar beat me to it.

Thor Simon

But this is of course absurd, since it greatly increases the cost of performing bulk operations across multiple tickets. At the very least there should be a per-project endpoint giving the possible set of transitions per issue type.

Nic Brough -Adaptavist-

Nonsense, it's not in the slightest bit absurd. Imagine two issues of the same type at two different points in the flow. Your "per project endpoint" suddenly becomes useless as it has to cover every single transition possible across everything.

Thor Simon

Not grasping how it would be "useless" to be able to obtain all the possible transitions for a project or even an issue type in one shot, rather than only those possible at one particular state in the flow. Why force the client to make multiple REST calls per issue when performing a single operation many times?

Joshua Landman

curl -u user:api-key -X GET -H "Content-Type: application/json" https://{your}.atlassian.net/rest/api/2/issue/{key}/transitions | python -m json.tool

--view your transition state ids--

curl -u user:api-key -X POST -H "Content-Type: application/json" -d @close https://{your}.atlassian.net/rest/api/2/issue/{key}/transitions

cat close

{

"transition": {

"id": {your status id}

}

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-core