Redmine

• This should be a request feature, not a defect.
• What's the need behind this feature? I don't get it. Thank you to be more precise.

Sorry. It's a feature indeed.

The specific need behind this the need to organize people within companies, and make it possible for users to inherit permissions from the company. We would like to add all of our customers of development projects to our redmine instance, but with different access levels.

Is it a bit more precise now? :)

Thanks,

Tommy

I've stumpled into similar needs to have more fine tuned permission levels inside projects to the customers.

For example in "Project X" I'd like to add customer accounts to be able to leave tickets and show their own tickets but not the rest that are submited by our company, our partner etc. So, similar permission feature like the "Edit own notes".

This would give a nice start in commercial permission tuning ;)

I vote this feature to be part of 0.8 roadmap. :)

So far in its own tree (work/groups), but it seems very stable. Undergoing testing/QA for regressions until Friday 9th. of may.

I checked out the work/groups branch and gave it a test run. So far it looks good.

I think Users should be able to be a member of many Groups. (many to many relationship). Having users be able to inherit permissions and roles from their associated groups is a big wish/feature for me but I'd need to be able to add the same User to multiple Groups.

Having this functionality is kind of a blocker for me. Else I'd be pushing hard for it to become a service for my organization (large higher education institution) I could see these groups representing classes, project groups, administrative departments, or more ad hoc stuff.

May I ask how things are going with this feature? It seems to have been implemented in the working branch, but when will it be rolled back into trunk? Is there some sort of issue which is holding this up? Thanks...