Feature #4015
openMake app settings overridable at project level
0%
Description
Allow some application settings (eg. Theme) to be overridden at project level.
Files
Related issues
Updated by Jean-Philippe Lang almost 15 years ago
- Target version set to 1.0.0 (RC)
Updated by Richard Schulte almost 15 years ago
+ 1
- Theme
- Trackers/Statuses/Workflow
- Enumerations
- Roles and Permissions
Haha yea, a laundry list, I know. Just the top two would be great.
Updated by Michael Koch almost 15 years ago
+1 and agree with Richard. This would be a great feature (and much needed for our project!)
Updated by Nikolay Kotlyarov almost 15 years ago
- Trackers/Statuses/Workflow
- Enumerations
- Roles and Permissions
Updated by Nikolay Kotlyarov almost 15 years ago
Workflow enhancements related to #559
Updated by Anton Statutov almost 15 years ago
IMO, the main settings need to override are columns displayed in the issue list.
Updated by Nikolay Kotlyarov over 14 years ago
Jean-Philippe Lang wrote:
Allow some application settings (eg. Theme) to be overridden at project level.
Which settings do you mean by "some"?:)
Updated by Mischa The Evil over 14 years ago
Updated by Richard Schulte over 14 years ago
Just wondering, what settings are you all honing in on?
Updated by Eric Davis over 14 years ago
- Target version deleted (
1.0.0 (RC))
Removing from 1.0. This hasn't been completed and 1.0 is feature frozen.
Updated by Marcelo Fernandes almost 14 years ago
+1 I do need enable/disable 'Documents' Section per project.
Updated by Matthew Burton over 13 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.
Updated by Etienne Massip over 13 years ago
- Assignee deleted (
Jean-Philippe Lang) - Target version set to Candidate for next major release
Updated by Brad Rushworth over 12 years ago
Jean-Philippe Lang wrote:
Allow some application settings (eg. Theme) to be overridden at project level.
For everyone's info, there is a plugin that allows user-selectable themes and it works great:
Updated by Thomas Robbs about 12 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.
Updated by Dipan Mehta over 11 years ago
+1. This would be a great leap forward in the Redmine's capability. A strong request to have this.
Also add #850 as a related issue.
Updated by Toshi MARUYAMA over 11 years ago
Updated by Dipan Mehta over 11 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
Updated by Toshi MARUYAMA almost 11 years ago
- Related to Feature #8095: Allow overriding the default text formatting in each project added
Updated by Toshi MARUYAMA almost 11 years ago
- Related to deleted (Feature #5624: the Text formatting configuration in each project.)
Updated by Toshi MARUYAMA over 9 years ago
- Related to Feature #7360: Issue custom query: default query per instance, project and user added
Updated by Toshi MARUYAMA over 9 years ago
- Related to deleted (Feature #7244: Default query per project)
Updated by Mizuki ISHIKAWA over 4 years 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_text
is how to get the application settings, andproject.setting_welcome_text
is how to get the settings for each project.project.setting_welcome_text
returns the same result asSetting.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.
Updated by Mizuki ISHIKAWA over 4 years ago
- File draft-4015.patch draft-4015.patch added
The patch I intended to attach at #4015#note-27