ROLES: Restrict issue list for user role according to private/public flag of project

Question

ROLES: Restrict issue list for user role according to private/public flag of project

Closed this issue 8 years ago · 10 comments

I think we should restrict issue access for normal users depending on the private/public flag of the project (which we already have). Since this flag already does something similar to the project itself.

That way we can control if a project is really public (like an OpenSource project where everyone can see what's happening) or more company internal (where issue reporters like clients or testers should only see what they've created)

Answer 1 · 2016-07-06T09:29:45.000Z

Can you provide more details here. How do you want to use the project flag and issue access?

Answer 2 · 2016-07-06T17:45:06.000Z

Ok I described that in #116

Answer 3 · 2016-07-23T03:17:48.000Z

I just tried the "internal" feature. Right now it seems that my user2 does still can see issues created by user1 in the listview of a project.

Answer 4 · 2016-07-27T09:44:36.000Z

I'm unable to replicate the issue in your last comment. I have setup a projects (Internal) with issues created by manager, user 1, & user 2.

If I login as Manager ==> I see everything.
If I login as User 1 ==> I only see issues created by the user 1.
If I login as User 2 ==> I only see issues created by the user 2.

Answer 5 · 2016-07-27T19:24:34.000Z

That's weird. I just tried that with the latest 2.10.
When we go to 'Projects' -> Active Projects -> -> then on the right side to "Open Issues" -> here you see all issues. No matter who created it or what status they are in.

Answer 6 · 2016-07-27T20:38:06.000Z

Can you post some screenshots of the users profile details, project edit form and open issues page to compare with what I have.

Answer 7 · 2016-07-28T00:28:43.000Z

I'm moving my demo instance online. But when I did it I receive this error after deleting an issue:

FatalThrowableError in QueueTrait.php line 73: Call to a member function isOpen() on null

Answer 8 · 2016-07-28T09:46:37.000Z

The above issue should be fixed in develop-2.10 branch

Answer 9 · 2016-07-28T19:25:31.000Z

Works again. Thanks.

I'm doing several things right now: Providing a test instance for both of us under develop.tinyissue.org, finishing the first draft the tinyissue webpage, working with helmut on the design.

I've cancelled travelling to Kaiserslautern on weekend because I want to provide you with the new design samples too.

Answer 10 · 2016-08-05T22:41:08.000Z

Closed for now. Further issues should be treated seperately.