Is it possible to limit user browsing so that a user only can see other users which are in the same group or in a configurable group/groups? We do not want to grant the "Browse Users" global permission so that every user can see every other user for @ mentioning. But without the "Browse Users" global permission the mentioning doesn't work
No, you can't limit the group visibility to "same as me"
Atlassian have not even tried to implement it. It is a bit of a pain for certain cases, but there's massive logical problems with implementing it. Off the top of my head:
Sort of. You can apply security schemes to issues that limit access. You can setup a default security scheme. Check out https://confluence.atlassian.com/jira/configuring-issue-level-security-185729623.html to start.
I'm afraid that is a non-starter. Working out "who is in my project" becomes exponentially difficult because of Jira's flexibility, and, quite often, people are using mentions because they want to draw in someone who is not "in the project".
I would like something that skips groups and uses its own rules. I should be able to group users into silos and people can only see people in their silo. With the option to make any silos globally available if necessary (e.g. everyone can see the support team silo, even when they're not a support person)
No, it does not.
It checks if a user has view issue, and create issue. Project "users" can be a lot more complex than that. Those are relatively simple checks, optimised, nothing to do with other users, and are absolutely not "is user on project" checks.
Maybe I don't fully understand this, but when a user opens the dashboard, or the list of Projects, there is a check for what projects their see. Surely this trickles down to each project's People (and Groups) list. So it's not that crazy.
But, again, I may be seeing things.
Yes and no.
I'm saying that there is no need to restrict users, you should be talking about what you allow them to do. And yes, it's complex and painful to do this by project.
If you're worried about users seeing each other, you currently have to turn off "browse users" as a global option.
If collaboration is justification for this defect then then why JIRA has roles and permissions??? ;-))) Let's collaborate everybody with everybody
What about NDAs and other information security restrictions that exist on the projects?
JIRA should allow for collaborators to see only what they are allowed to see.
It is a bit weird that even if you use custom permission scheme, and lets say give a specific group of external users (client) specific permission to Manage Watchers and View Voters and Watchers, they still can't do that because global permission says only our internal groups can browse users.
Like a bunch of others in the community, our clients must not see a list of all JIRA users, but they should be able to see/mention/add to watchers users who are specifically assigned to that project like how it works for Assign a user.
Sorry for reopening this, but I am desperately trying to find a solution, it still evades me.
This thread is not about who can see projects, its about who can see the user lists.
Sorry, belted "send" too soon on that, and then went into a tunnel with no reception. Here's what I should have said before posting:
Jira does not restrict, it only grants permissions at the project level (issue security is a different story).
In theory, this is really simple, because all you have to do is set the permissions so that "users matching a rule can see the issue". That grants permission. It is often by saying something simple like "users in the role of 'user' in the project can see it", and then putting the users (or groups) you want into that role in the project.
Jira ships with some terrible defaults which automatically grant access to anyone with a login, and before you can use the simple, sane and reasonably intuitive rule above, you have to unpick these dreadful defaults, so that you can actually do it.
There's a good guide to it over at https://community.atlassian.com/t5/Jira-questions/JIRA-Software-project-permission-restrict-user-access-to-one/qaq-p/779572
No apology is needed on your side - I'm happy that you found a thread that looked related and you asked. This conversation is messy and unclear (unintentionally of course), and it's better that you asked and got a pointer, than stayed quiet and got nothing.
On my side, an apology was the right thing - my accidentally shortened post was terse and grumpy-looking and gave no useful guidance. It wasn't what I wanted to leave you with, and I'm hoping the correction was better!
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