Can I prevent users from creating a specific issue type, so that only an automation can create it?
Hello @Phil Bustin
Are you working with a Team Managed project or a Company Managed project?
Natively Jira does not allow you to restrict issue types per user (or user group or project role) such that the issue type doesn't appear in the drop down in the Create Issue interfaces.
With a Company Managed project you can add a Validator to the Create transition to block the creation of the issue at the point when they click the Save button. That type of option is not available with a Team Managed project.
There is a change request about implementing such functionality here:
https://jira.atlassian.com/browse/JRACLOUD-44557
You can find other discussions of this same topic in the communities.
I believe it might be possible to do with third party apps if you are open to that solution. You might be able to implement it with ScriptRunner Behaviours.
Sorry--I forgot I already posted essentially the same question. The answer is supposed to be to configure the issue type as a sub-task, if I've got that right.
Your response seemed instantaneous! Please my addendum below. I will discuss this with another admin here.
I think in your addendum you are referring to your other post here:
https://community.atlassian.com/t5/Jira-Software-questions/Can-I-configure-a-workflow-so-that-creation-of-its-issue-is-only/qaq-p/2612305
Sub-tasks are the only type of issue that cannot be selected in the Create Issue dialog. Those issues can be created only by starting from the parent issue and click the Create Child button.
All other types of issues can be created from the Create Issue dialog.
Is your use case only about creating sub-tasks, or does it concern creation of other types of issues?
My goal was to try to allow creation of a specific issue type only by automation, and that does not appear to be possible or at least easy. I can settle for making the issue type a sub-task, thus only allowing creation from a parent; and training users to create a parent issue with a field value that triggers the automation that in turn clones the issue to the sub-task.
I hope that answers your question.
If your use case is, as you have stated in the other post:
"Can I configure a workflow so that creation of its issue is only from a parent?"
...then Sub-task type issue are the only issue type that natively always require a parent. But tracking the work as a sub-task type issue has other impacts that may be undesirable in your use case.
The question from your other post really is not the same as the question in this post - requiring a parent is not the same as blocking people from creating a particular type of issue.
If you are truly interested in answering the question in this post, please describe your use case. What problem are you trying to solve? Why is it necessary to prevent the creation of a particular type of issue by people and only create it through Automation.
It looks like you're new here. Sign in or register to get started.
