Permission Denied error when adding a user picker field to API call

[Pamela Gustavson]

Hello, 
I am trying to figure out why I am getting an access denied/permissions error when I add a field to an API call. 

Context -- I am using an external tool (Sailpoint) to create tickets for onboarding and offboarding users. I use the same template with the same jira fields for both tickets.

Problem -- When I create an onboarding ticket WITH the supervisor (user picker), I get a 401 unauthorized error "You do not have permission to create issues in this project."

• It works when I create the onboarding ticket WITHOUT the supervisor field. 
• It works when I create the offboarding ticket WITH the supervisor field. 
• It works when I manually create onboarding tickets WITH the supervisor field when using the UI (with the API user login). 

The issue type is the same for onboarding and offboarding tickets. 
The API user is a project admin in the space.
There are no issue-specific permissions.  

What can I be missing? 

Thank you!
Pamela

[Tuncay Senturk _Snapbytes_]

Hi @Pamela Gustavson 

Have you checked if the Supervisor custom field has different configurations for onboarding vs. offboarding issues? Go to Contexts and Default Values and ensure the field is available for the Onboarding Issue Type and project. Other than that, I can't say more as I need to see the request payload.

[Pamela Gustavson]

We use the same issue type/project for both (just a general request) -- so it is available in the form and it does work for the onboarding ticket.

Let me scrub some of the data and I will post the payload shortly. 

[Tomislav Tobijas]

Hi @Pamela Gustavson ,

It might be worth checking if this API call/user with which you're authorizing to create issues has Browse Users and Groups global permission.

Apart from that, not much comes to mind.

Does this happen only to this particular user picker field or do you experience the same issues with other user or group picker fields?

Cheers,
Tom

[Pamela Gustavson]

It only happens with this one user picker field. 

We populate the employee user picker field on the same form and it works just fine. 

And we populate the employee user picker field AND the supervisor user picker field in the offboarding ticket -- also works fine. 

[Pamela Gustavson]

It does have browse users and groups permissions.

[Tomislav Tobijas]

Hey @Pamela Gustavson ,

Apologies for leaving this in the cold. The laptop went to a service and alongside that, all 'open' questions too. I've just got it back so I'm seeing some things just went under the radar from my side. 😕

Have you managed to find a solution? If not, you could potentially reach out to Atlassian Support so they can check it out.

Cheers,
Tobi