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; } } }

Reduce issue types list on the create screen depending on the reporter

Sergey Shmarkatyuk

Is it possible to hide some issue types on the create screen for specific user groups?

For example, I have 'bug', 'epic', 'story', 'task', 'test', 'architecture task', 'analysis task' in the list of available issue types:

I want to be able to display only 'bug' issue type for testers.

Is it possible to achieve in JIRA?

Accepted answers

Renjith Pillai

No, that is a big constraint of JIRA. This forum has so many posts asking for the same. Just do a search.

All comments

Renjith Pillai

No, that is a big constraint of JIRA. This forum has so many posts asking for the same. Just do a search.

Sergey Shmarkatyuk

Could you please post at least one link to the related question or jira issue? I could manage to find one. Thanks in advance!

Renjith Pillai

Google search gave me this, (but I guess you will be disappointed that there no real solutions in any of these)

https://answers.atlassian.com/questions/33259/permission-to-create-specific-issue-type

https://answers.atlassian.com/questions/118786/how-to-disable-the-issue-type-in-jira

https://answers.atlassian.com/questions/33436/any-workarounds-to-do-permissions-by-issue-type

https://answers.atlassian.com/questions/120489/keep-issue-type-in-workflow-scheme-but-do-not-allow-it-to-be-created

https://answers.atlassian.com/questions/119531/customizing-the-sub-task-types-based-on-the-issue-type

https://answers.atlassian.com/questions/109710/controlling-the-visibility-of-issue-types

https://answers.atlassian.com/questions/52475/is-there-a-way-to-limit-the-issue-types-that-a-user-in-a-particular-group-can-create

https://jira.atlassian.com/browse/JRA-5865

Stacy_4zfv2v

This would be a very useful capability. Hope Atlassian are listening.

Priyanka Lavania

Hi Sergey,

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira