Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

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?

2 answers

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?

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.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Team-managed projects

4 steps to get actual statuses on the Jira board.

Jira   is a powerful tool   that helps teams to plan, manage, and report on their work.   We love using Jira, especially for its ability to track issue progress. But how to monitor the...

1,199 views 10 14
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