I'm trying to figure out how to add a new project, but keep some specific user from having access to it. We're using the default software permission scheme and I don't see how to remove "any logged in user" from the "browse projects and issues within them" without ruining access for everyone in our system.
Can someone please advice how I would add a new project and only grant access to specific users (or deny access to other specific users)?
The flow for this seems extremely convoluted. Going to user management and being able select a user, then select check boxes for projects they can view is what I'd expect from a service like this, rather than having to hop around multiple screens and adjusting permissions for everyone...it's all just very unintuitive.
Anyway, any help here would be greatly appreciated.
In the Browse Permission of a project's Permission Scheme you can add a group, project role or individual user. Lot of people prefer giving this right to a Project Role like Users or Developers and then Project Administrator can add/remove users in the Project role to give access to the users without asking the JIRA Administrator again and again.
It is a bit more layered than that, and the general advice is "do not use groups in permission schemes"
To expand on that, the default set up in JIRA is below. Most of us change it, as it's a pain in the neck.
Net effect - anyone who can log in can use the project. To fix it, remove the global group from the project role, replacing it with either individual users, and/or other groups.
In this case, what you're trying to do is remove access that's been granted by "any logged in user" and narrow it down to known groups. So you need to remove the generalised stuff and add back groups and individuals that you want to allow access to.
Thanks again for the response, Nic. Unfortunately, I still can't figure this out...
I tried removing the "any logged in user" group from the "browse projects" permission and added a role to it instead but, as I expected, that just means no one without that role can view any project or any issues and those with that role can view all projects and all issues.
I'm at a complete loss here and giving up...thanks for your help, everyone.
Hopefully Atlassian will make this a MUCH easier process someday, but for now, I guess we're stuck : /
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
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