Jira Transition issue using postman

Question

Hi Everyone,

I have treid performing the Transition issue using postman.

If I am just passing the Issue id or key as path param and transition id in request payload then the API is working.

For example

request payload for Transition issue API

{"transition":{"id":"11"}}

this case is working fine.

but If I am trying to pass fields as well then I am getiing an error.

for example: requets payload for Transition issue API

{"transition":{"id":"11"},"fields":{"summary":"testSummary"}}

then I am getting an error.

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

Can some please let me know why so?

Is transtion issue just need only one fields in request payload i.e transition id ?

Please let me know.

Abhishek Jaswal_lysv7o · Answer

I have gone through the API doc again and found the get Transition API tells about the fields that can be updateable during do transition API operation.

I have made a call to API

https://<domain>.atlassian.net/rest/api/3/issue/DEMO-3/transitions?expand=transitions.fields&transitionId=11

but getting the below result.

{
"expand": "transitions",
"transitions": [
{
"id": "11",
"name": "Backlog",
"to": {
"self": "https://devbcone.atlassian.net/rest/api/3/status/10003",
"description": "",
"iconUrl": "https://devbcone.atlassian.net/",
"name": "Backlog",
"id": "10003",
"statusCategory": {
"self": "https://devbcone.atlassian.net/rest/api/3/statuscategory/2",
"id": 2,
"key": "new",
"colorName": "blue-gray",
"name": "To Do"
}
},
"hasScreen": false,
"isGlobal": true,
"isInitial": false,
"isAvailable": true,
"isConditional": false,
"fields": {},
"isLooped": false
}
]
}

Fields are coming null.

Can someone please let me know why so?

Juan Manuel Ibarra · Answer

Hello, Apparently your api call sends a new value for the summary field.
If this field is not editable, that is, it is not in the edit or transition screen or the user does not have edit permissions, it will throw you that error.

You can exempt these validations using the QUERY PARAMETERS

overrideScreenSecurity and overrideEditableFlag in the url