Jira Spoke 'Create User' activity error: "You must specify the products that user can access"

Steve Brown1
Tera Expert

Hi Community, 

 

The Jira Spoke 'Create User' Activity is erroring with the below and I'm at a loss to what is causing the error:

{
    "Action Status": {
        "code": 1,
        "message": "Error:  You must specify the products that user can access. (Process Automation.fb6442fe77391110cc985228c81061d6; line 4)"
    }
}

This Activity has previously worked via a manual test however, nothing in terms of configuration has changed. 

I have since tested the Activity manually entering the values and via a FLOW gathering the values from a submitted Request Item.

 

Would this something that needs to be configured within Jira as the Create User activity doesn't required anything in relation to specifying a product?

SteveBrown1_0-1717492063174.png

#jira

#jiraspoke

#atlassian

#integrationhub

#createuser

14 REPLIES 14

Kieran Anson
Kilo Patron

Referencing the Cloud Jira API documentation, product details is a mandatory requirement as part of the payload. You'd need to clone the action and add in the field requirement. I'd also raise a support case with ServiceNow to have the spoke updated (assuming you're on the latest release) https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-users/#api-rest-api-2-user-post

Hi Kieran, 

 

I tried doing what you suggested, but it has made no difference to the outcome when trying to create a new User account.  I have successfully setup Add/Remove a User to a Group and Remove a User, but this is a sticking point. 

 

We're building this integration without any documentation as I can't find anything online!  Would you be able to share any links to any further documentation you have?

 

Many thanks.

Steve

Hey Steve,

I was just following the docs I linked previously. You may want to speak with your Jira SME to understand whether you're integrating with the cloud version, or data center. The link I shared is for cloud (which most people are now on) but your client/customer may be on a self-hosted instance which uses a different API setup.

Okie dokes, many thanks for that link as its far more that I had to use!

Yeah, we're cloud to cloud.  I'm just confused as I have created numerous of test user accounts during the development previously without having to send a Product until recently.