patch to extend user roles

Submitted by quanvn on 2014-04-10

I love Webissues, it UI is nice and clean; and it run fast and smooth. However, I use webissues in working with my students in thesis supervision, so I need more detailed roles (apart two default currently):
- Those who can only read the existing issue
- Those who can only give comment and add file to report their job
- Those who can give comment, add file, and also can change attribute of existing but cannot create new one

So I decided to patch directly to the code. It turns out to my surprise that this can easily be done (It took me about 20 hours). I cannot attach the details sine the system say not accept but if you are interested please drop me an email

I'm very interested. Please see my other topic here: webissues.mimec.org/node/722

I hope you can upload the patch to any cloud service and post the link here for the benefit of everyone.

Thank you.

Currently Webissues follows the principle: member see all. The permission scheme only restricts what they can do with the issues, and my patch respects this principle. It only defines a finer right to manipulate issues, not right to access (see) the issues. Extending things in this way would require a full ACL system (?).

As suggested by techana and also from my own need, I extend my patch to allow view level. So now it is possible to make people can view only issues they created or assigned at folder level. Unfortunately, this patch still does not work with desktop client so I have to disable it and use web client. I will handle this to Michal so he will decide if it should be implemented in future version.
@techana: please contact me if you want to try it

I definitely want something like this implemented in a future version, but I'm still not sure what's the best way to manage permissions in a simple but flexible way. Also the desktop client makes things more difficult, because it has it's own local database which is incrementally updated from the server, and issues may become available or not available to a user when they are edited or the permissions are changed, so this is quite complicated.

Regards,
Michał