Redmine

I've seen several similar feature requests. I am sorry for adding another one.

Now, regarding the issue, after giving it a second thought, I conclude that by giving the ability to project managers to determine whether a module would be available to non-members or not would be a feature that would resolve most of the situations where a team needs a part of its project space being private to project members only. Such a feature would serve as a small, but highly effective, per-project permission override.

For example, at the Project->Settings->Modules tab, the project manager could have the option to deny access to each module for non-members.

I believe that this could be implemented easily. Also, I think most feature requests about being able to set permissions on a per-project basis would be covered. But, of course, other special needs cannot be covered by such a solution.

• Public project
• with private SVN repository

It would be very useful to have project-specific settings for the system-roles (non member, and anonymous/public).

While one could create specific roles with specific permissions just for one project, those system-roles can't be duplicated and assigned for specific roles.

So there is no work-around for allowing SVN access to non-members and public for all projects, but not allow SVN access (view and changesets) to project members only in specific projects.

That feature would greatly help in not-yet first-released open-source projects and in collaborative commercial projects.

Please email me if we can help co-sponsor that feature.

Well, we leverage the project nesting feature to work around that, and create say a project project1 and subproject called project1-private, the first being public, the second private. That way, we can have whatever we want either private or public, depending on the need.

Seems, this is related to #1853 / #2076?

and also to #4015

+1

and i believe this is duplicate of #850