Hi
1.Being an admin i create jira boards and create group and add user specific to board.
I have multiple jira board with different clients and have different users overall
* Now every user when click on Quick search (top right side) he can search any other user by typing in search bar, which is violation of our business.
How to solve this issue. we want user particular to that board should access his group users not all.
or we totally remove this search bar.
We need real quick reply. thanks,
When you say search every user, do you mean search for issues other users are assigned to - or search for other users on the platform?
-------------
If it's the former - you need to restrict user access per project, rather than per board. See:
-------------
If it's the latter - you'd need to remove the global permission "Browse users and groups" from all client-based users. If users have this permission, they can browse all users on the site without exceptions.
Removing it will mean things like @mentioning users, sharing issues, locating assignees, etc will no longer function. So you'll need to weigh up if this will materially impact your client's experience depending on how they use the information they can see in your instance.
To see how global permissions work - see this page
Ste
Hi everyone.
Thanks for your reply.
I have setup group, permission and role for every jira board. Every client's jira board has different users.
But when someone click on top search and type name he can see other client's board user which is violation of our contract he must see his own board users only.
Rest everything is working fine but this search bar is showing all users.Also see global permission as well
globally these users have rights rather than specific groups. i have no issue like admin can see all users but jira board specific user should not see other users.
thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If users do not have the "Browse Users & Groups" permission, they won't be able to select users from user picks which aren't permission-based.
For the Assignee field within a project, it will still have users they can select but should be limited to any user who has the "Assignable User" permission within that project.
As for the search bar - it's locating text data as opposed to user data. I'd test it as if the user can't see the issue it might not bring up the name of the user as an option, but then again it might still be parsing the whole issue list even with permissions sets.
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi @Ste Wright
For the Assignee field within a project, it will still have users they can select but should be limited to any user who has the "Assignable User" permission within that project.
yes its happening. no issue.
As for the search bar - it's locating text data as opposed to user data. I'd test it as if the user can't see the issue it might not bring up the name of the user as an option, but then again it might still be parsing the whole issue list even with permissions sets.
Issues data is also coming as per Jira boards assigned to particular user.
say, Jira User name= Alex.
Boards Permission= Human Resource, time space
Now when Alex type lets say John( John is user in BallTracker jira board) he can view him.
when i click on "View All Filter" it works as expected ie it only show board specific users.
when i click on show more button able to view ALL JIRA USERS. ( it should only show Human Resource and time space group users)
I am just only concerned about this part. How can I restrict Alex not to view John on above described scenario and for every other interface its working as expected.
thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I do not believe that you can remove the quick search. And I do not see any suggestions in the public backlog to do so.
Have you reviewed the documentation and use cases for how to restrict project access for teams? You can find that information here:
Best regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.