Some PAT tokens are returning 200 with no transitions data on API to specific Jira projects

Paula Cruickshank

Firstly we have to use the Token. Username/Password is not an option given our company security organisation. 

We have been using a token for some time as part of API calls from Groovy to transition tickets in a Jira project

• The first call gets the available transitions for an issue
• The next actions the transition, using the found transition ID

The problem is that this code is also to be applied to other Jira projects.

Whilst it works fine to transition issues in the existing Jira project, it returns no transitions data for the new projects. The user that the token relates to has the same role assignment in both projects. Using a token for a different user (with the same role credentials) in the new project, also works exactly as expected

Using the existing token in the new project returns [] as the available transitions, despite the http response code being 200. 

Radek Dostál

There is a difference somewhere, you're getting an empty json array - which is a valid response. If it's not roles, is the permission scheme the same or different? If not permission scheme, are the workflows different - perhaps there are conditions on the transitions blocking the user?

 

What you're describing says 100% to me that there are either permission related errors somewhere.

 

Try opening the issue with the user in browser - if you can't do any transitions, it's permission related. You could try the permission helper from issue view to see why the user cannot transition issues - it should find something. If it doesn't then I'd suspect a status property, or transition properties from that status.