-
Bug
-
Resolution: Fixed
-
Medium
-
2.6.1 Enterprise
-
-
-
2.06
-
When i add the "Current Reporter" to the "Browse Project" Permission of one project. This project instantly becomes visible to ALL users(via the project table portlet), if they have any kind of permission to see this project or not.
So all users can see this project, but can't see any issues within it. Thats not very good, as we want to keep our customers strictly seperated from one another and we have a lot of projects. That would be very confusing if you see lots of projects in your dashboard, but only one or two of them are relevant to you and the rest is empty.
- has a regression in
-
JRASERVER-34389 Regression - "Browse Project" permission for "Reporter" grants users to see projects they are not permitted to.
- Short Term Backlog
- is related to
-
JRASERVER-8950 "Current Assignee" on Browse Permission creates security hole
- Closed
-
JRASERVER-12051 Adding group selector permission makes project name visible to everyone
- Closed
-
JRASERVER-14941 Users without permissions can browse projects that they do not have perms to if custom field-user picker
- Closed
-
JRASERVER-4927 Suppress Error Message, when user has no right to browse project
- Closed
-
JRASERVER-14424 Separate permissions for issue filtering and project display
- Gathering Interest
- was cloned as
-
JRASERVER-34389 Regression - "Browse Project" permission for "Reporter" grants users to see projects they are not permitted to.
- Short Term Backlog