Feature #270
closed
project module configuration
0%
Description
How about the ability to add/remove modules on a per project basis? Example: projectA has Documents and News modules
only, while projectB has all Modules (Issues, Reports, News, Change Log, Documents, Members, Files), while projectC
has Issues, Reports and Change Log modules only, etc. etc.
Why?
1) This could allow/promote the idea of developing custom modules in the community. You know, modules that are not
necessarily a good match for every redMine deployment. Examples: integrate with existing calendar system Module or
read/display from a series of RSS feeds Module, or Sugar CRM integration Module, etc., etc.
2) It will allow projects to be configured to simple or complicated functionality specifications as necessary
--/--
Years ago, I wrote a project management system in Java where modules could be added/removed on a per project basis.
I'm trying to learn Ruby now. Anyhow, I'm going to attach a snipped screenshot to offer a visual display of what I'm
trying to describe.
Thoughts?
Files
Updated by Jean-Philippe Lang over 17 years ago
It's a good idea. Il though about it one day but didn't had time
to add this feature.
I think it should be added in a future release.
Regards
Updated by Todd McGrath over 17 years ago
I have a potential solution in place for this feature
request. See Bug 7501.
Updated by Jason Huebel about 17 years ago
Love this idea. It offers the potential of making redMine even
simpler for the user.
However, #1 above implies a module API with the example given.
I hope that this isn't something that's currently planned, since
it could potentially make redMine too complicated. Right now,
it's easy to use and understand. redMine isn't
a CMS/portal/framework.
Updated by Jean-Philippe Lang over 16 years ago
Project module configuration is possible as of r725.
A project module (eg. issue tracking, news, wiki,...) is a set
of permissions that can enabled/disabled at project level.
For each project, modules can be enabled on the project settings
view ('Modules' tab).
This requires a specific permission: 'Select project modules'
(if this permission is turned off, only Redmine administrators
can choose which modules a project uses).