Per-repository permissions

[leoluk]

I am running a Mantis instance which hosts different projects with different users and different permissions, but all repositories are visible to everyone.

It would be nice to be able to assign a repository to a project, and then have the project permissions apply for the repository as well.

[dregad]

I agree that this would be a nice and useful feature, however it is not a small undertaking because the plugin was initially not designed to restrict this access.

Unfortunately I do not have time to work on this at the moment. Feel free to submit a patch.

[Sieberkev]

I really would like this feature too :+1:

[leoluk]

Had to meet a deadline, used Redmine instead. Maybe I'll write a patch for this in the future.

[evilchewits]

Binding to project might be not a good idea (we use a single repository for several projects). Would not it be a better approach to introduce "view_state" flag for repositories, changesets, etc.?

I'm not confident about how this feature works with other MantisBT entities (projects, bugnotes, etc.), so I'm wondering. Is it easier to implement? Will it cover the case described above and other common situations?

[xiexj788]

I would also like to know how to deal with this problem. Does anyone know how to solve it? Thank you very much

[kjorsh]

Any kind of user permissions will be great. May be similar to a projects assignment - user may have repositories assigned or vice versa - each repository has a list of users who can see it