Project

General

Profile

Actions

Feature #270

closed

project module configuration

Added by Todd McGrath about 18 years ago. Updated about 17 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:

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

project-modules.gif (7.62 KB) project-modules.gif Todd McGrath, 2008-02-03 11:03
Actions

Also available in: Atom PDF