I'm looking for a part-time remote job.

Hire me


I'm the author of:

Mastering Redmine is a comprehensive guide with tips, tricks and best practices, and an easy-to-learn structure.

Check the book's project or

Buy the book

Social pages of the book:

By buying this book you also donate to Redmine (see this page).


Follow me:

Hack goes public

Did you ever want to restrict access to some projects maintaining role names?.. I.e. not by creating special roles like ”<Project name> developer”?.. I did!

What I also wanted to do is to make some projects more restrictive for non-members… That’s the situation when the problem really occurs! You can’t assign a different role for non-members! As well as you can’t assign a different role to anonymous users… That’s Redmine limitation!

And like other limitations this one can also be evaded… with my Role Shift plugin!

How does it work and what does it do?

To change the default behaviour the plugin performs “role shifting” and it does this transparently to Redmine/ChiliProject. A visible role seems to remain the same but its permissions get replaced with shift role’s permissions. So visually restricted projects won’t differ from others (e.g. same “Authors”, “Contributors” etc).

This was not the idea to do things this way! That was how the Redmine API allowed to change roles (I replace role permissions when Redmine/ChiliProject requests a role for a user). Of course, it’s a hack! While it seems to work fine for me because it’s a hack there can be issues! And for this reason the current version is beta!

Please read main Wiki page for how to use the plugin correctly (safe).

Also if you are interested in future changes please subscribe to this project using the form on the sidebar which is provided by my Subscription plugin.

 

Comments

Also available in: Atom

Add a comment