openproject

Commit Graph

Author	SHA1	Message	Date
Oliver Günther	73441bfea0	Continued conversion of type form	5 years ago
Wieland Lindenthal	904f709ea3	Remove BCF thumbnail from default form configuration	5 years ago
Oliver Günther	2474978636	[30151] Perform attribute group validations when changed Also adds a better error message to let users find out which attribute is invalid. https://community.openproject.com/wp/30151	6 years ago
Oliver Günther	79befe97b3	Bump capybara and rspec	6 years ago
Oliver Günther	f42ff4bdd6	[28543] Validate Type#attribute_groups in contract Validating attribute groups is only relevant when creating or updating the type in the administration. There's no need to validate this in the type itself. https://community.openproject.com/wp/28543	6 years ago
Oliver Günther	b08a5874f5	Remove project responsible and type	6 years ago
Jens Ulferts	93b0d34a36	handle errorenous embedded queries on form configuration	6 years ago
Oliver Günther	d05c1ff087	[27940] Don't sort members of attribute groups This will result in wrong orders https://community.openproject.com/wp/27940	6 years ago
Oliver Günther	e8216bb16e	[27611] Restore relations tab (#6300 ) * [27611] Restore relations tab * Remove default children query [ci skip]	7 years ago
Oliver Günther	ca8ef3ed7c	Fix creating a task without resetting the group objects When creating a task with custom_fields through the factory, it will create the task and hit the attribute_groups during validation, resulting in them being cached and no longer changing due to the custom_field_ids being changed.	7 years ago
Oliver Günther	0904ed5dbf	[27487] Properly reset custom fields when resetting attribute groups CF on types can still be set through `custom_field_ids=` and is used in e.g., a number of tests as is the standard way to define custom fields. This is no problem until resetting the attribute groups, where the default attribute groups will contain the custom fields formerly defined. Thus, explicitly resetting the attribute groups must also reset the custom_field_ids. https://community.openproject.com/wp/27487	7 years ago
Jens Ulferts	d7a4e16007	prevent saving attribute_groups if they are the defaults	7 years ago
Jens Ulferts	919badbf81	keep attribute_groups on changes to position	7 years ago
Jens Ulferts	7051fe771e	fix resetting the attribute_groups	7 years ago
Oliver Günther	1acccb444a	Fix attribute groups model now that fixed children query is removed	7 years ago
Oliver Günther	7c3766e694	Fix form configuration specs	7 years ago
Oliver Günther	1ae368c31a	Render attribute and query groups in backend	7 years ago
Jens Ulferts	4fc7e9d439	linting	7 years ago
Jens Ulferts	17d7d2c511	handle query saving, updating, deletion	7 years ago
Jens Ulferts	5a5e3494f9	turn attribute group into dedicated object	7 years ago
Jens Ulferts	fa2b0fa1d9	clean up templated filter values	7 years ago
Jens Ulferts	14dd5c77f4	introduce a :context value for parent filter	7 years ago
Jens Ulferts	941c1ec25d	fix type attribute_groups validation	7 years ago
Jens Ulferts	5e7f1f8df9	hardwire default group to every attribute_group	7 years ago
Jens Ulferts	9e4f5053bc	hack having the children table provisioned from the backend	7 years ago
Jens Ulferts	a33b0bbbbd	WIP - return Query as an attribute group * only default query for now * only returned when no custom configuration is applied * start to turn attribute groups into ressources	7 years ago
Oliver Günther	6ef4211e77	Bump copyright to 2018 (#6171 ) [ci skip]	7 years ago
Oliver Günther	9fabaaaf13	Show only attributes from the type attributes and status, project	7 years ago
Oliver Günther	8956700408	[25374] Remove attribute visibility	7 years ago
ulferts	3f4bfb52ee	memoize custom_field evaluation for default_attribute_group (#5627 ) This can become quite costly when the same calculation is done 200 times (for each custom field that could be active on the type) [ci skip]	8 years ago
ulferts	0c0b16508b	Fix/bump representable (#5465 ) * bump reform and roar -> bumps representer * adapt to changed validation interface * disable initializer patch for now * adapt to changed representable attr interface * can no longer have private methods inside a representer * private no longer possible for representer * bump reform * wip - restyle validation * remove commented out patch * apply injection as prescribed * reactivate reform error symbols patch * remove patch to Hash superfluous wit ruby 2.3 * remove outdated human_attribute_name patch * whitespace fixes * adapt filter name after removal of human_attribute_name patch * adapt filter specs to no longer rely on human_attribute_name patch * fix version filter name * remove reliance on no longer existing human_attribute_name patch * use correct key in journal formatter * remove private from representer * adapt to altered setter interface * reenable i18n for error messages in contracts * no private methods in representer * defined model for contracts * fix validaton * instantiate correct Object * define model for contract * circumvent now existing render method on reform * replace deprecated constant * patch correct reform class - not the module - via prepend * refactor too complex method * replace deprations * remove remnants of parentId * prevent error symbols from existing twice * adapt user representer to altered setter interface * adapt watcher representer to altered setter interface * remove now unnessary patch * adapt setter to altered interface * adapt spec * fix custom field setters * remove parentId from wp representer As the parent is a wp resource, clients should use the parent link instead * adapt spec to changed valid? interface * remove parentId from wp schema * replace references of parentId in frontend * remove TODO [ci skip]	8 years ago
Oliver Günther	94234bd5ee	[25432] Correctly transmit hasDefault to frontend (#5603 ) The default value for CFs is '', which is obviously not nil despite not being a default, however the frontend only _always_ shows the attribute when it is required and has no default. This PR also adds a 'always visible' flag to the form configuration when the CF is set required. [ci skip]	8 years ago
Oliver Günther	5d50acc50e	[25288] Re-add translations to default attribute groups (#5515 ) * [25288] Re-add translations to default attribute groups Uses symbols to mark internal attribute groups and translates them in the schema representer to the user's locale. * Extend form configuration front end for translated default groups * fixing specs * fix feature spec for attribute groups * Add symbol test to attribute groups [ci skip]	8 years ago
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

50 Commits (ce7e9d510e2005d62813a69291e234ead9d81224)