As Nic says, you need to remove permission. JIRA works on the grant permission model. There is no deny permission option. Many people put the jira-users group in the permission scheme which gives everyone who can logon whatever permission the group is put in. That route leads to issues like this. That group should only be used if you are absolutely sure you will ALWAYS want everyone to have that permission, which is seldom the case.
You don't configure setting on the group. You configure the PERMISSION SCHEME. As Nic and I said, you need to FIRST remove any group that has logon permissions from the permission scheme. Then add the new group to the permissions you want. This may require having more than one permission scheme.
I use project roles so I can have just one permission scheme. There may be roles some projects don't use, but I find in the long run it is easier to manage JIRA as a whole. It also allows project leads to add/delete users from the roles instead of needing JIRA admins to add/delete group membership.
When you created the group did you give it logon rights? If so, any new user created will automatically be put in the group (built in behavior) so you'll soon have more people accessing your project that you don't want to.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs