Restrict the creation of a work item to one specific user

[Corinne Guibert]

Hello

We have people that are not always using the correct work item. 

We would like to restrict the creation of the work item "Task" to one specific user. Is it possible ? How ?

The only option I'm seing right now is an Automation that will delete the Task if not creating by the correct user but it's not clean

thanks for your thoughts 

[Marc -Devoteam- · Accepted solution]

Hi @Corinne Guibert 

Ootb this is not possible, other then the mentioned automation.

You would require an app to extend workflow options.

Such an app could set a validator based on user being in a group or role in the project, to limit this.

Make sure  the work type Task has it's own workflow, so you can set such a validator.

Or you could built a behaviour related to a specific user.

Solutions requires apps, for option 1;

• JSU
• JMEW
• JWT
• Scriptrunner

For behaviour option, Scriptrunner is required

[Arkadiusz Wroblewski]

You can’t restrict Create by issue type using Jira permissions alone — the Create issues permission applies to the whole project, not to specific types like “Task”.

The clean workaround (no automation/delete) is to block creation via the workflow “Create” transition for the Task issue type:

1. Make sure Task uses its own workflow (separate from other issue types).
2. Go to Project settings → Workflows and edit the workflow used by Task.
3. Open the Create transition → Validators.
4. Add a Permission validator (or “User is in group/role” validator, depending on what you have available).
5. Choose a permission that only the allowed user has (commonly something like Administer projects, or a project role/group you can keep very small).
6. Ensure only that user (or a dedicated group) has that permission/role in the project.

anyone else can try to create a Task, but Jira will stop it at creation with an error message "nothing gets created", so you don’t need to delete anything afterward.

If you’re on a team-managed project, options are more limited; in that case the usual solution is either a separate project for Tasks or an app (e.g., ScriptRunner Behaviours) to hide/limit the issue type on the create screen.

[Corinne Guibert]

@Arkadiusz Wroblewski  : Thanks for the solution . I implemented it.

I have ScriptRunner Behaviours install on the instance but I never use it so yours with the rule is faster and easier to implement