Can we lock down who can create specific task types?

[Kevin Shaffer]

Inside of one of our projects, we have both task and helpdesk tasks. We'd like to make it so that users can only submit helpdesk type tasks, and not accidentally create "tasks" which are used for project work and not added to our helpdesk queue. Is this a possibility? Or do we need to rethink our process?

[Joe Pitt · Accepted solution]

Jira doesn't have issues level control. There is a work around where after the users attempt to open an issue you deny it when they save it. But that tends to make the users mad. Most long time Jira users opt to create a different project for the tasks and link the task to the related helpdesk issue 

[Rebekka Heilmann _viadee_]

Hi @Kevin Shaffer 

in Standard Jira, you could use a Transition validator in your workflows, to make sure the reporter has a certain permission: How to restrict the creation of an issue based on issuetype | Jira | Atlassian Documentation
Your project team would need a permission that your "customers" don't have and then you use that in addition to the "Create issue" permission in the validator.

If you want to restrict it to project roles, you will need Addons like Adaptavists Scriptrunner: Restrict Creation of Certain Issue Types to Members of a Project Role - Adaptavist Library