Creating an Issue Security Scheme

Question

Hi, I want to create a restriction where none of the project users can create issues, except the project leads and admins. I created an Issue Security Scheme and then an Issue Security Level that states only project users cannot create issues.

Now when I entered the project where I want the Issue Security Level to be integrated, I can't seem to find the Issue Security in the project sidebar.

Is it that I don't have access to this? Or the issue security is moved someplace else?

Thanks for helping out!

Dave Mathijs · Answer

No problem @Ryan Paul . Are you able to create/change the configuration so it answers your requirement(s)? If my answer helped you, thanks to accept the answer.

Ryan Paul · Answer

@Dave Mathijs

Hi! My bad! I thought this issue security was meant for restricting users (not team leads) from creating tasks.

I noticed a few of my colleagues are creating their own tasks and this is messing up the due date/sprint.

I want them to come to the team leads and let us know that they want to add a few tasks for them instead of them adding the tasks. This way we (team leads) can keep track by adding new tasks for them or/ shifting the new task to a new sprint.

Since the create issue option is available to them in the backlog, they are creating tasks and assigning the tasks to themselves. I want to restrict them from creating tasks.

So after going through some tutorials online, I assumed this issue security scheme will help me from deactivating the create issue in the backlog.

Nic Brough -Adaptavist- · Answer

This is not quite what issue security schemes are for, and they can't stop people creating issues.

There's an error somewhere in what you say here, so I'm not sure what you have actually tried to do.  You say "I created an Issue Security Scheme and then an Issue Security Level that states only project users cannot create issues."

You can't do that.  A security level is a collection of rules that identify people, they have nothing to do with creating issues.  Permission schemes control who can create issues.  So I think you mean you've said only certain project users can create issues.  Is that right?

If so, then you've probably solved your problem already, by saying "create issue: project lead, administrator"