16 Commits (1f480faa27b537a3a93e30f44fdc38d529c30f9e)

Author	SHA1	Message	Date
Jens Ulferts	2672fb20ae	allow empty groups in type form configuration	8 years ago
Jens Ulferts	4ca69221a4	cache attribute map calculation	8 years ago
Oliver Günther	1cfa120192	[19714] Make priority part of form configuration ... This allows users to completely disable the priority, if they wish. As it will always receive a default value, it is internally still a required field.	8 years ago
Oliver Günther	93dcd386f4	Remove usage of CF translations	8 years ago
Oliver Günther	01351399d5	Cache all_work_package_form_attributes ... Especially with lots of custom fields, this is otherwise called once per represented WP and is quite costly.	8 years ago
Oliver Günther	8d381651c8	Fix specs	8 years ago
Oliver Günther	1666b587da	Display custom fields in parallel + autoscrolling	8 years ago
Oliver Günther	ba9c0ce58f	Allow custom fields to be added through type	8 years ago
Oliver Günther	2666f8dd70	Avoid enabling new CFs by default	8 years ago
Wieland Lindenthal	7130927de9	Prevent validation errors when removing costs plugin for instance	8 years ago
Oliver Günther	6eaa291f88	Generate default group labels with Setting.default_language	8 years ago
Oliver Günther	e62e14feb5	Extract visibility into separate class for consistency	8 years ago
Oliver Günther	ea6fed8a5f	Improve validation of group configuration	8 years ago
Oliver Günther	e4f0cb6634	Fix AR method name duplication	8 years ago
Oliver Günther	ff3b5166ae	Correct translations for default groups	8 years ago
Oliver Günther	8220d43bbf	Add custom sub-models for attribute constraints and groups ... This allows plugins such as backlogs and costs to integrate into the grouping while restricting while they are visible. The problem here is that on a global admin page, the plugin's attributes should be available, however in a project context, they should only be added when the respective module is active.	8 years ago