Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,363,771
Community Members
 
Community Events
168
Community Groups

Why transitioning an issue via the rest api clear the description?

Edited

Hello!
I'm using the rest API to transition issues after a deployment. 

I'm making a POST request on :

/rest/api/3/issue/<issue_id>/transitions

With this body :

{ 
"transition" :
{
"id": <transition_id>
}
}

 
The transition is correctly done, however, the description field of the transitioned issue is cleared afterwards.

It's not because of a post-function in the transition, there's none.

Does anyone knows why the description is cleared?

3 answers

0 votes

Hello @Alaric Calmette, I reproduced the reported issue and finally resolved this bug.

Hello! Thanks for the answer,

Yes the problem still exists, the differences between your curl and my code is that I don't include the no-cache header, and the call is made via Faraday ( a ruby gem )

Other than that, I don't see any reason why your code would behave differently than mine.

Hmm. That's interesting.

Are you trying this for a Next-Gen project?

The issue appeared on a non next-gen project, I haven't checked if it's also happening on next-gen projects.

Are you using Jira Software Cloud or Jira Software Server?

I'm on Jira Cloud

Can also confirm as a Jira Cloud user that this issue happens, seems to be on transitions where we have a screen that appears with required fields before the transition can occur. In our use case we don't need/want to change the values of these fields, and it's okay if the transition fails due to a missing required field.

Hi Alaric,

We tried to reproduce the issue but in our case, the description still remained the same.

We executed the following request:

curl -X POST \
 https://<jira-instance-domain-name>/rest/api/3/issue/<issue-id>/transitions \
 -H ‘authorization: <Auth-token>’ \
 -H ‘cache-control: no-cache’ \
 -H ‘content-type: application/json’ \
 -d ‘{
    “transition” : {
        “id”: <transition-id>
    }
}

Can you please confirm if your problem still exists?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events