working cross project with multiple teams and disciplines and you only want specific teams and/or roles to be able to create certain issue types becomes a multiple workflow nightmare.

Abstract example:
users primarily working on project can create all issue types

users external to project:
user A can create issue type A and X and Z
user B can create issue type B and X and Y and Z
user C can create issue type C and Y and Z

Workflows to accommodate:

workflow(s) for regular issue type(s)
separate workflow for issue type A ( user A )
separate workflow for issue type B ( user B )
separate workflow for issue type C ( user C )
separate workflow for issue type X ( user A, user B )
separate workflow for issue type Y ( user B, user C )
separate workflow for issue type Z ( user A, user B, user C )

it only gets worse the more complex this structure needs to become, this is a simple example.
The administrative overhead to manage these workflows, and the risk of making a mistake increases exponentially as more issue types and conditions have to be accounted for.
A simple control to dictate who can create what eliminates this administration and security headache entirely

For us it would be really helpful to restrict the creation of epics in certain projects to a group of user or project role. A validator function for the create issue transition is necessary and we were wondering why it's not implemented yet.

Hello, I can't understand why Atlassian ignores all useful request and implement random and useless features. It looks like they want their partners sell more paid addons that covers basic needs ( basic querying, reporting, managing rights for creating some issue type....). Atlassian boord runs this company as if it is Ryanair.

While waiting for this functionality to be available in Jira out of the box, maybe you could consider the app we developed - Field Rules for Jira. It includes the Hide issue types rule, which enables you to hide specific issue types on the Global Issue Create view. Moreover, you can configure preconditions based on user groups, project roles, or individuals. I would appreciate it if you could give it a try.

i found a quick and dirty workaround : create an empty screen, attribute this screen to "create" for your restricted issue type, none can create since there isnt any compulsory field filled

they can still go around this by cloning or re-using an existing issue of that type but the "can't create, missing summary" message can serve as a soft warning to prevent the mistake

In the project permission scheme, there should be an option to choose the Issue Type, and apply specific permissions to them.  Project specific permission scheme is too broad and doesn't work in the real world.

Hello Everyone,

If you are having scriptrunner, in your workflow update parameters of the 'ScriptRunner Script' Validator for "Create" transition.

Restrict to User Groups

 
user.groups.includes('usergroup')

Our pain point is to be able to block the creation of Stories for specific teams.

The suggested workaround is horrible from many aspects. 

9 years with no traction on a basic ask, typical of Atlassian

The workaround is horrible; nothing prevents the user from filling out the create form, only to receive an error message upon submit.

This is SIMPLE: you already have the capability to define the validator rule - QUERY THE RULE WHEN DRAWING THE CREATE SCREEN.  

For each IssueType in Project

Hi,

We have Projects configured with issue types starting from,

Level 1 - Objectives,

Level 2 - Initiatives,

Level 3 - Epics,

Level 4 - Stories, Defects, Problem etc

Level 5 - Subtask

So in a Project we don't want all to create Objectives and Initiatives. How can we restrict this?

I hope this is basic requirement.