Make app settings overridable at project level
|Target version:||Candidate for next major release|
Allow some application settings (eg. Theme) to be overridden at project level.
#12 Updated by Matthew Burton almost 10 years ago
+1. I think this is the feature that would make Redmine a more viable option for enterprises (like mine). When you have many different users and missions, it's hard to find one set of enumerations, roles, and trackers that makes everyone happy yet at the same time isn't overly cumbersome for administrators. This would also relieve the IT office from sole responsible for administration, as it would give many administration permissions to project managers.
Been lurking for a few months and really love RM. I created an account just so I could speak up for this feature.
#16 Updated by Thomas Robbs over 8 years ago
+1 and +1 Matthew Burton.
It seems the burden is mainly due to the "project-y" settings being mixed with the "application-y" settings. For example, configuring "Default columns displayed on the issue list" in the application level settings.
I'd suggest just separating settings along these lines into two camps:
1. Redmine Settings (app level stuff)
2. Project Templates (project level stuff)
#2 effectively starts out as a "Default Project" template, defined by the existing default "project level stuff" settings.
A new installation would be effectively transparent, save some reorganization of the settings and adding the notion of "templates".
An existing installation would, on upgrade, and ideally for me, give me the option to save each of my existing projects' configurations as new templates (default name = project name, editable), or use an existing template of my choice.
I could also see this notion extending to Trackers and Categories as there are similar requests that pull the solution towards needing to be sufficient for their needs as well. Might be helpful to map the entities and their configuration options to make the solution more obvious.
#21 Updated by Dipan Mehta almost 8 years ago
There are just about so many issues which asks for 'Per project configuration'. Here is a list:
- #3452, - Email notification config (alongwith #7349, #8331)
- #1144 - Time tracking activities
- #552 - Document categories
- #12347 - Calculation logic of issue %done ratio
- #12044 - Notification Mails per Project
- #9194 - default issue list view layout
- #7244 - default query
- #3316 - Language! ...aaha
- #432 - Custom Email templates and email settings
#27 Updated by Mizuki ISHIKAWA 9 months ago
I attach a patch to override application settings at the project level.
This is not a tested or fully implemented patch, it was created to get your design reviewed.
- Add Setting.project_id column
- Setting for each project if setting.project_id exists, application-wide setting if setting.project_id is nil
Setting.welcome_textis how to get the application settings, and
project.setting_welcome_textis how to get the settings for each project.
project.setting_welcome_textreturns the same result as
Setting.welcome_text if the record of @Setting.where(project_id: project.id, name:'welcome_text')does not exist
This patch allows you to change "Isuses list defaults" on
http://<url>/projects/<project_id>/settings/overwrite_global_settings page as a trial.