Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Unable to update issue status using JIRA API..

Hi All,

I am trying to update the status of the issue with the below REST URL,

JIRA Server URL/rest/api/3/issue/{IssueKey}/transitions?expand=transitions.fields

Using the below Json Format.

{
"update": {
     "comment": [
               {
                   "add": {
                  "body": {
                 "content": [
             {
                "type": "paragraph",
                "content": [
              {
                   "text": "Transition Update from JIRA API..",
                   "type": "text"
             }
        ]
         }
      ]
    }
     }
  }
 ]
},
"fields": {
"assignee": {
"name": "abc"
},
"resolution": {
"name": "Postponed"
}
},
"transition": {
"id": "10201"
}
}

But unable to update the Issue status and comments. Giving the below error..

"The remote server returned an error: (400) Bad Request." 

Can anyone pls suggest on the same?

Thanks

Vishnu

 

3 answers

Hello @vkalakuntla 

The URL and json payload seems fine. However, are you sure Jira server URL/context is right or are you using Http POST method?

Because 400 error codes are related to the missing URLs/resources.

0 votes
Warren Community Leader Nov 18, 2019

Hi @vkalakuntla 

When I transition items via the API, I also have &transitionId=XXX added to the call, so please try

/rest/api/3/issue/{IssueKey}/transitions?expand=transitions.fields&transitionId=10201

Hello @Warren ,  @vkalakuntla 

 transitionId was used in json payload.

"transition": {
"id": "10201"
}

So, it would be redundant to use it in Url querystring.

Would it be because of rest api version? Could you also try using 2 instead of 3 as below?

 /rest/api/2/issue/{issueIdOrKey}/transitions?expand=transitions.fields

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Opsgenie

Opsgenie and Amazon team up to launch new DevOps Guru integration - now available!

We’re proud to announce that our integration with Amazon DevOps Guru is now live. The Amazon and Opsgenie product teams have worked together to build a deep integration between Opsgenie and the new...

233 views 0 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you