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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

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,556,218
Community Members
 
Community Events
184
Community Groups

Jira API issue while transitioning

I am trying to use JIRA API to transition my issue with a state id, using bot with all required access. I also tried with admin access. The board configuration looks good.

Also, there are no rules/conditions set between the transition states, still I am unable to transition my issue only to one particular state. While, it gets transitioned to other states successfully using the same API and parameters.

 

The error I get is as follows - 

```
[ERROR] JIRAError: JiraError HTTP 400 url: https://xyz.atlassian.net/rest/api/2/issue/yyy-xxxxx/transitions
text: Can't move (yyy-xxxxx).
You might not have permission, or the issue is missing required information. If you keep having this problem, contact your Jira Administrator.


response text =

{ "errorMessages": [ "Can't move (yyy-xxxxx). You might not have permission, or the issue is missing required information. If you keep having this problem, contact your Jira Administrator." ], "errors": {} }
```

Is anyone else facing a similar issue?
I think this a bug to be resolved with the API.

0 comments

Comment

Log in or Sign up to comment