Project

General

Profile

Actions

Feature #39178

open

Issue visibility

Added by Hoang Tuong Tran about 1 year ago. Updated about 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Issues permissions
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:

Description

Hi everyone,
I have a scenario with Issue permission like this:
I have a Project A to store issues (Aa, Ab, Ac) but some issues is sensitive and can only show to some specific users (U1, U2, U3, U4, U5) and cannot show to other members in the project (each issues have their own privacy).

- In issue Aa (related to U1, U2): I set to Private then, change ' Issues visibility ' of U1, U2 to ' All Issue '. Then U1, U2 can see Aa;
- After 3 days, another admin create Issue Ab and Ac with ' Private ' activated and only want to show to U3, U4 so he have to change ' Issues visibility ' of U3, U4 to ' All Issue '.

Now this is a disater : U3, U4 can freely view Issue Aa which I don't want to show them vice versa with Issue Ab, Ac now show to U1, U2. U1, U2, U3, U4 now peeps others Issue and lead to Internal Fraud which I do not want from the beginning.

Hope you guys can understand the scenario above and have a solution.

Thank you, Have a nice day!

Actions #1

Updated by Bernhard Rohloff about 1 year ago

Why not solving this by creating two separate non-public subprojects and adding the appropriate members to them? Then you have exactly the behavior you describe.

Actions

Also available in: Atom PDF