Limit issue types based on user group? Jira ScriptRunner

[Rodrigo Gomez]

Hello, I have been trying to limit the issue type based on the user group to specific project with no success via Behaviours on Jira ScriptRunner.

Example User belongs to the group JIRAtests should only be available to create issuetypes A and B, while users that do not belong to JIRAtest should be able to create issue types A, B and C

I was trying to achieve this via Scriptrunner behaviors but no success at all.

const issueTypeField = getFieldById("issuetype")

const user = await makeRequest("/rest/api/2/myself");

const { accountId } = user.body;

const userGroups= await makeRequest("/rest/api/2/user/groups?accountId=" + accountId);

const groupNames = userGroups.body.map(({ name }) => name);

// Select the group that the specific issue types will be shown for.

const group = "JIRAtest";

if (groupNames.includes(group)) {

    issueTypeField.setOptionsVisibility(["10040", "10011"], true)

}

Is there another way or is there something wrong on the code?  thanks

[Kristian Walker _Adaptavist_ · Accepted solution]

Hi Rodrigo,

I can confirm that in Jira Cloud, the Behaviours feature does not support Jira Service Management, which means there is no way to restrict issue types on creation in Service Management at this time.

You can see the products and projects types behaviours supports in the documentation page located here.

Also, the example script here shows how to restrict issue types to users in certain groups in supported project types.

I hope this information helps.

Regards,

Kristian

[Trudy Claspill]

Hello @Rodrigo Gomez 

I think the syntax of your line here is incorrect:

const userGroups= await makeRequest("/rest/api/2/user/groups?accountId=" + accountId);

Looking at the example code in this video from Adaptavist:

https://www.youtube.com/watch?v=lkYZU-LQums

... the code should be

const userGroups= await makeRequest("/rest/api/2/user/groups?accountId=${accountId}");

[Rodrigo Gomez]

I have modified but seems this is not compatible with Jira Service Management

thanks for the help

[Joseph Chung Yin]

@Rodrigo Gomez -

In addition to what @Trudy Claspill pointed out on the syntax error, please kept in mind that in JSM what users sees are the Request Types to create his/her issues for your JSM project.

Request Type is based on the IssueType allowed in your project.  So are you asking to restrict request types access based on group association?  If, take a look at this reference link out of the box for JSM to restrict request type access for issue creation (without using Behavior setup) -

https://support.atlassian.com/jira-service-management-cloud/docs/add-or-remove-restrictions-on-request-types/

Hope this helps.

Best, Joseph Chung Yin