Norman Browse

0 views

Skip to first unread message

Ailene Goldhirsh

unread,

Aug 3, 2024, 1:57:21 PM8/3/24

to restripovi

Over more than 8 years now, eBoighar continued to fulfill people's need for academic, professional and personal books. Currently, books range from textbook, guidebook, question banks, exam preparation guide to fiction, non-fiction and religious, Islamic; from nursery to PhD level. When book lovers need some rare books, they request us through Find My Books page. We happily assist. We also sell many useful learning tools and accessories. Our medical tools and aprons continue to make thousands happy throughout the year. Convenient electronic payments, cash on delivery, easy, just and generous returns & refunds... all earned love of buyers. We solve complaints with tenderness and sincere hearts. We commit to best price and quality.

We work hard to create equal opportunities of succeeding for all students. For all academics, professionals and individuals. For all buyers, suppliers and patrons, regardless of their locations. We spread capabilities in the most economic and innovative means possible. So Join Us today. Search, browse and buy. Send Us your idea. Together, we build a beautiful future. Read Inside Close Email It Browse's Introduction to the Symptoms and Signs of Surgical Disease (Color) Norman L. Browse

I have a particular issue regarding the Browse Projects Permissions: even if I grant permissions just to a restricted group of users, the ones that couldn't see the project can see the project inside the all project list. Ok. He can't see all issues inside the project

I have the same issue. I have 100 projects under a Permission Scheme, all of the items have only groups for permission. However, the user (that is not assigned to any group yet) can see the list of projects. I don't want this to happen. Users should only see the projects they have access to. Any thoughts?

Sadly, there is no built-in step-by-step wizard to set up the permission schemes according to your needs, therefore most Jira enthusiasts start with the default settings, create loads of projects and start worrying about security later.

Depending on how many users/groups/projects you have, this "tabula rasa" might take some time once, but save you a lot of headache afterwards. In the end, your users will only see issues/resources/projects, because you explicitly allowed them to.

If you want to hide a project, you need to remove the user's browse access to it. Check the permission scheme for the project and look at who has "browse". You need to make the user *not* match any of the rules in there.

Your user *must* be matching one of the rules that allows browse rights.

I'd re-check all the role memberships of course, but I suspect that they either have "create issue" rights, which would allow them to become a reporter, or they are selectable from the custom field you have in the scheme which would also give them the right to see an issue in that project.

as you suggested, I noticed that there was an "assignable" rule associated with all users in Jira (it was the only one). I changed it and re-indexed all project, but, unfortunately, it still not work...

Hello, it seems i have same problem.... User is not in project users as user or as a group member, project permissions and still can see project itself. It seems that its visible only on project list screen.