nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to restrict some issue types to some groups ?

LaurentV

hi,

We want some of our issue types to be used only by some user groups. Is there a way to do that ?

Regards,

Accepted answers

Jobin Kuruvilla [Adaptavist]

This is not possible in JIRA. See https://jira.atlassian.com/browse/JRA-5865

Look at the issue and its linked issues to find different workarounds.

Priyanka Lavania

Hi,

I solved this issue using Script runner's behavior, used below code in initializer and it showed Issuetypes based on logged in user, you can validate user against project roles or even groups

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.security.roles.ProjectRoleManager

import static com.atlassian.jira.issue.IssueFieldConstants.ISSUE_TYPE

def projectRoleManager = ComponentAccessor.getComponent(ProjectRoleManager)
def allIssueTypes = ComponentAccessor.constantsManager.allIssueTypeObjects

def user = ComponentAccessor.jiraAuthenticationContext.loggedInUser
def issueTypeField = getFieldById(ISSUE_TYPE)
def availableIssueTypes = []

//use this def and if code to check project roles
/*def remoteUsersRoles = projectRoleManager.getProjectRoles(user, issueContext.projectObject)*.name

if ("Testers" in remoteUsersRoles)
{
availableIssueTypes.addAll(allIssueTypes.findAll { it.name in ["Task", "Experiment"] })
}
*/

//use this def and if code to check groups
def remoteUsersRoles = ComponentAccessor.getGroupManager().isUserInGroup(user, "jira-administrators")
if (remoteUsersRoles) {
availableIssueTypes.addAll(allIssueTypes.findAll { it.name in ["Task", "Experiment"] })
}

else {
availableIssueTypes.addAll(allIssueTypes.findAll { it.name in ["Task"] })
}

issueTypeField.setFieldOptions(availableIssueTypes)

Hope this helps.

Regards,

Priyanka

All comments

Jobin Kuruvilla [Adaptavist]

This is not possible in JIRA. See https://jira.atlassian.com/browse/JRA-5865

Look at the issue and its linked issues to find different workarounds.

Dieter

Please be more specific about what the groups should be able to do (create issues, edit issues, view issues, transition issues...)

LaurentV

my question is about creating issues

Joe Pitt

As Jobin said, this isn't possible. There are some work-arounds in the jra-5865 he points to, but all have some kind of problem. the cleanist way, in my opinion, to do it is to put the different issue types in different projects since permissions are at the project level.

Dieter

So Jobin answer applies

Justin Leader3

Great answer!

Young Plugins

I recently developed a plugin that might help. I'm open for ideas to make it better. Cheers

Cindy_chmpmz

You can do this with workflow conditions if still needed.

Nagendra Dattatreya

Hey Cindy,

Can you elaborate on how to achieve this? I want to restricts "Support group" to create bugs but should not be allowed to create stories.

Thanks,

Nagendra

Swetha Bammidi_5t6kbj

Any solution on this

Cindy_chmpmz

You could use the addon Jira workflow toolbox to create a validator on the create transition.

Manmohan Gopal

If you are JIRA Admin, You can create issue scheme and associate your project to restrict issue types as you need. I have same issue and solved creating scheme.

Note: If you have already issue created which is not part of your required list then those will be prompted update to existing ones

Young Plugins_ya4bn5

Contact me on youngplugins@gmail.com for a good deal on the plugin "Issue Type Filters"

Alejandro Reyes

Scriptrunner has an option on behaviours to do this on their newest version:
https://scriptrunner.adaptavist.com/5.5.0.3-jira8/jira/recipes/behaviours/restricting-issue-types.html

Hope it helped.

Priyanka Lavania

I used behaviour to do this for groups, which worked like charm. Thanks

Priyanka Lavania

Hi,

I solved this issue using Script runner's behavior, used below code in initializer and it showed Issuetypes based on logged in user, you can validate user against project roles or even groups

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.security.roles.ProjectRoleManager

import static com.atlassian.jira.issue.IssueFieldConstants.ISSUE_TYPE

def projectRoleManager = ComponentAccessor.getComponent(ProjectRoleManager)
def allIssueTypes = ComponentAccessor.constantsManager.allIssueTypeObjects

def user = ComponentAccessor.jiraAuthenticationContext.loggedInUser
def issueTypeField = getFieldById(ISSUE_TYPE)
def availableIssueTypes = []

//use this def and if code to check project roles
/*def remoteUsersRoles = projectRoleManager.getProjectRoles(user, issueContext.projectObject)*.name

if ("Testers" in remoteUsersRoles)
{
availableIssueTypes.addAll(allIssueTypes.findAll { it.name in ["Task", "Experiment"] })
}
*/

//use this def and if code to check groups
def remoteUsersRoles = ComponentAccessor.getGroupManager().isUserInGroup(user, "jira-administrators")
if (remoteUsersRoles) {
availableIssueTypes.addAll(allIssueTypes.findAll { it.name in ["Task", "Experiment"] })
}

else {
availableIssueTypes.addAll(allIssueTypes.findAll { it.name in ["Task"] })
}

issueTypeField.setFieldOptions(availableIssueTypes)