Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Closed
nickbe opened this issue Jul 3, 2016 · 10 comments
Closed

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

nickbe opened this issue Jul 3, 2016 · 10 comments
Labels
change-request fix-develop
Milestone
2.9.0

Comments

@nickbe
Copy link

nickbe commented Jul 3, 2016

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)
@nickbe nickbe changed the title Restrict issue list for user role according to private/public flag of project ROLES: Restrict issue list for user role according to private/public flag of project Jul 3, 2016
@satrun77 satrun77 added this to the 2.9.0 milestone Jul 3, 2016
@satrun77
Copy link
Owner

satrun77 commented Jul 6, 2016

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

@satrun77 satrun77 removed this from the 2.9.0 milestone Jul 6, 2016
@nickbe
Copy link
Author

nickbe commented Jul 6, 2016

Ok I described that in #116

@satrun77 satrun77 added this to the 2.9.0 milestone Jul 6, 2016
satrun77 added a commit that referenced this issue Jul 18, 2016
@satrun77
Feature: allow to create a more restricted project visibility
428c419 
Fixes #123 #121 #116

Project can be set to internal only. This means users with role of "User"
can only see issue created by them. This is to allow manager and developer to work
on internal issues that should not be visible to users/clients of the project.
satrun77 added a commit that referenced this issue Jul 18, 2016
@satrun77
Feature: allow to create a more restricted project visibility
46292f9 
Fixes #123 #121 #116

Project can be set to internal only. This means users with role of "User"
can only see issue created by them. This is to allow manager and developer to work
on internal issues that should not be visible to users/clients of the project.
satrun77 added a commit that referenced this issue Jul 18, 2016
@satrun77
Feature: allow to create a more restricted project visibility
88e84c5 
Fixes #123 #121 #116

Project can be set to internal only. This means users with role of "User"
can only see issue created by them. This is to allow manager and developer to work
on internal issues that should not be visible to users/clients of the project.
satrun77 added a commit that referenced this issue Jul 18, 2016
@satrun77
Feature: allow to create a more restricted project visibility
79ec68a 
Fixes #123 #121 #116

Project can be set to internal only. This means users with role of "User"
can only see issue created by them. This is to allow manager and developer to work
on internal issues that should not be visible to users/clients of the project.
satrun77 added a commit that referenced this issue Jul 21, 2016
@satrun77
Feature: allow to create a more restricted project visibility
be68983 
Fixes #123 #121 #116

Project can be set to internal only. This means users with role of "User"
can only see issue created by them. This is to allow manager and developer to work
on internal issues that should not be visible to users/clients of the project.
@nickbe
Copy link
Author

nickbe commented Jul 23, 2016

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.

@satrun77
Copy link
Owner

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.

@nickbe
Copy link
Author

nickbe commented Jul 27, 2016

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.

@satrun77
Copy link
Owner

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

@nickbe
Copy link
Author

nickbe commented Jul 28, 2016

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

@satrun77
Copy link
Owner

The above issue should be fixed in develop-2.10 branch

@nickbe
Copy link
Author

nickbe commented Jul 28, 2016 •
edited
Loading

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.

@nickbe
Copy link
Author

nickbe commented Aug 5, 2016

Closed for now. Further issues should be treated seperately.

@nickbe nickbe closed this as completed Aug 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
change-request fix-develop
Projects
None yet
Milestone
2.9.0
Development

No branches or pull requests
2 participants
@satrun77 @nickbe