ChiliProject is not maintained anymore. Please be advised that there will be no more updates.
We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.
Provide a nice way to disable some functionalities like the boards (Feature #261)
Description
Our project hosting serving is quite new in our community, which means we have already had boards for years, creating forums within the main forums tree. Thus we do not use ChiliProject's boards, that would be duplicating services, which is not good. As of now, I let the right to project managers to change the modules used by their project, including the boards. As I do not want to see them used, I warned them against these and made a bad trick in the source tree to make them not working (renaming the views folder...). I'd like to have a nice option to prevent them from using the boards. Is something of that kind possible?
I think it could also be extended to others built-in functions as the wikis, if anyone needs it.
Related issues
| related to Feature #767: Remove the artificial separation between Settings and Con... | Open | 2011-12-11 |
Associated revisions
Redirect to issue page after creating a new issue
Previous behavior was to redirect to the issue list with a "successful
creation" message. This patch will redirect to the page for the
newly-created issue, still with the "successful creation" message.
This matches the behavior after editing an issue and also provides
instant feedback for the user to see if anything went wrong.
Closes #261 and uses the patch contained therein
git-svn-id: http://redmine.rubyforge.org/svn/trunk@1243 e93f8b46-1217-0410-a6f0-8f06a7374b81
History
Updated by Aleksey Zapparov at 2011-03-05 07:07 pm
Manager is just another role. So you can restrict "Manager" role and disallow to modify project settings for example.
PS But probably it would be great to have Wiki, Forum etc as a separate core modules. So anyone will be able to turn on or off them globally according to his specific needs.
Updated by Thibaut Cuvelier at 2011-03-09 06:53 pm
Sorry, I forgot to come and answer here.
This is a solution I also tried, but it is quite a work for me to enable/disable modules for each project as the requests arrive. Also, that way, project managers often forget that other modules can be enabled (or even never knew).
The solution of core modules one can turn off easily would be great!
Updated by Tom Rochette at 2011-07-01 11:47 pm
In the Administration, go to Roles and permissions. Create a new role for your "project manager" and uncheck the Select project modules in the Project section.
Updated by Thibaut Cuvelier at 2011-07-04 04:43 pm
This is not a solution as previously explained: I need the users to be able to enable functionnalities on their own. They must be able to choose to enable some modules. _
Updated by Eric Davis at 2011-07-06 11:18 pm
Thibaut Cuvelier:
So you want to be able to completely turn off the forums module so that even "project managers" can't enable it in Project > Settings?
Updated by Thibaut Cuvelier at 2011-07-07 08:29 am
Eric Davis wrote:
So you want to be able to completely turn off the forums module so that even "project managers" can't enable it in Project > Settings?
Yes, exactly.
Updated by Felix Schäfer at 2011-07-07 10:41 am
We really have to get around fleshing out the different parts as core plugins… (that would be the nice way…)
Thibaut: I could provide you with a not-so-nice way to disable different modules, but only if you are somewhat rails/ruby-savvy as it involves a core patch.
Updated by Thibaut Cuvelier at 2011-07-07 11:00 am
Felix Schäfer wrote:
Thibaut: I could provide you with a not-so-nice way to disable different modules, but only if you are somewhat rails/ruby-savvy as it involves a core patch.
Well, I try to understand a bit of Ruby to solve some problems I meet, but that's all I'm up to :/.