147 Commits (140275ba7dc24f4605a2c8542952d08bd97e1cd4)

Author	SHA1	Message	Date
Jens Ulferts	baa7e99d1d	cleanup timelines data	7 years ago
Jens Ulferts	dd80b0d670	remove planning_element from permitted_params	7 years ago
Oliver Günther	a0150fffa0	Remove timelines	7 years ago
Jens Ulferts	6fdd122534	merge wp tree and relations into typed_dag ... Instead of having the tree/hierarchy information for work packages and the relations between the work packages separated into two tables all the information is now stored in the relations table. To support this, the typed_dag plugin is used. Notable changes: * relations_to and relations_from are swapped. relations_to has all relations that point to another work package (from_id = work_package.id) and relations_from contains all relations that lead to the work package from another one (to_id = work_package.id). This change is merely in the code. The db information is left untouched. * For follows/precedes to_id and from_id are swapped in the db. Because of that, "follows" is now the canonical name instead of "precedes". This is done so that hierarchy relations and follows relations point into the same direction which allows to easily detect cyclic relationships that would lead to infinit scheduling. * the columns `root_id`, `lft`, `rgt` do no longer exist in the wp table. * the column `relation_type` does no longer exist in the relations table. * For every type of relation a column (integer) does now exist in the relations table (e.g. hierarchy, block, follow) * Separate associations exist for every type of relation into two directions. E.g. Work packages following the current one can be accessed via `work_package.precedes`	7 years ago
ulferts	c0b709530c	Fix/replace deprecations (#5533) ... * replace alias_method_chain * remove deprecation silencing * bump controller-testing * introduce permitted params for settings * replace various deprecations in controllers * remove deprecation silencing for legacy_specs * remove `puts` from spec * replace deprecated access to errors * remove unnecessary AR::Parameters usage in spec * specify error to expect * replace deprecations * replace deprecated action calls in legacy function specs * replace deprecations in functional controller tests * replace deprecations in controllers/controller_specs * remove params parser which does not seem to be in effect It is registered for the content type :exclude which makes no sense as it should deal with :json. The desired behaviour of the api dealing with parsing errors is working with or without the code. * replace deprecations in unit specs * replace alias_method_chain [ci skip]	7 years ago
ulferts	75f501e897	Fix/custom field lacking options (#5768) ... * enforce having at least one custom option for a list cf Removes the hand written nested attributes handling by accept_nested_attributes_for. Removes the arbitrary boundary of having 500 custom options. * i18n for custom option mgmt [ci skip]	7 years ago
Oliver Günther	39e11c72dc	Create backend for help text CRUD	7 years ago
Oliver Günther	8956700408	[25374] Remove attribute visibility	7 years ago
Jens Ulferts	5b9efd6efe	rewrite permitted_params_spec	8 years ago
Jens Ulferts	f5531d2c44	fix switching month on calendar	8 years ago
Oliver Günther	93dcd386f4	Remove usage of CF translations	8 years ago
Oliver Günther	e4f0cb6634	Fix AR method name duplication	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
Wieland Lindenthal	bbbb9726c1	Latest WIP [ci skip]	8 years ago
Wieland Lindenthal	673a60d18b	Dom structure to input type hidden	8 years ago
Markus Kahl	f5a57e3f42	list custom field normalisation and multi select	8 years ago
Oliver Günther	36aebac777	Add `:attr_admin` to permitted params ... Otherwise, setting them from UI will fail.	8 years ago
Oliver Günther	7cf11bb689	Update copyright notice	8 years ago
Markus Kahl	91b2645460	fixed pagination	8 years ago
cklein	9c59621c1e	Auto hide popups. ... https://community.openproject.com/work_packages/24152	8 years ago
Jens Ulferts	fc3f04f7c1	remove dead code	8 years ago
Oliver Günther	4fab8974ce	Fix legacy search controller spec after permitted params	8 years ago
Oliver Günther	8391a9c0d2	Use PermittedParams to allow search parameters	8 years ago
Jens Ulferts	c00a2602e2	fix permitting custom field value params	8 years ago
Oliver Günther	117dfa4e2d	Legacy: Fix functional projects controller spec	8 years ago
Jens Ulferts	05f0bc2a5b	replace deprecated merge!	8 years ago
Oliver Günther	45c3521a51	Ensure configuration is loaded	9 years ago
Oliver Günther	b64aa048eb	Use Proc to infer available type attribute visibility ... Otherwise, migrations will break when a plugin tries to register new params.	9 years ago
Markus Kahl	148a3fff14	work package form configuration	9 years ago
Jens Ulferts	061a71bb32	fix setting custom values on version	9 years ago
Stefan Botzenhart	5ccdbaa3ef	Permit parent_id only if user is allowed to create subprojects	9 years ago
Stefan Botzenhart	a42e89f987	Permit parent_id for project	9 years ago
Stefan Botzenhart	e13641bdd2	Improve according to rubocop	9 years ago
Markus Kahl	3c17be3261	retain old behaviour per default to be safe	9 years ago
Markus Kahl	e482eee87e	don't require custom field container per default	9 years ago
Markus Kahl	aa58b7deca	allow arbitrary custom field IDs	9 years ago
Markus Kahl	d4293532d9	do not block time entry custom fields	9 years ago
Oliver Günther	a339373d0f	Allow responsible_id in projects settings ... This fixes two issues: 1. `responsible_id` was missing in allowed params for projects controller / settings. 2. When the value is not set from Rails, undefined is showing. There may be a workaround solely in the frontend, but for now I return (none) to the autocompletion as a responsible name instead of an empty string.	9 years ago
Oliver Günther	353039fcfe	Allow PermittedParams to receive new keys from plugins ... Previously, PermittedParams allowed only the extension of existing keys with new attributes from plugins. Since we now need to extend strong_params from global roles in impermanent memberships, we can prevent load-order dependencies by injecting a new key in the permitted params hash into the core.	9 years ago
Mohamed Wael Khobalatte	e10cc2d6ad	Pass project_id instead of project instance to version_attributes	9 years ago
Mohamed Wael Khobalatte	0e72ec4243	Move to ruby1-9 syntax once and for all	9 years ago
Mohamed Wael Khobalatte	18ac022927	Add specs for new strong_params methods	9 years ago
Mohamed Wael Khobalatte	6f1d668c39	Fix issue with versions/new being not accessible	9 years ago
Mohamed Wael Khobalatte	602dd749e3	Ensure versions params play well with plugins	9 years ago
Mohamed Wael Khobalatte	a1bf92212d	Fix legacy and cucumber specs failing because of strong params	9 years ago
Mohamed Wael Khobalatte	972b04d86e	Refactor to allow for strong params ... We no longer need attr_accessible.	9 years ago
Oliver Günther	04ff74ac24	Refactor PermittedParams to class	9 years ago
Jens Ulferts	b0a86a69c2	refactor types action on projects controller ... * Introduced a service to reduce complexity in the controller * Used permitted params to ensure params syntax * Introduced a scope for querying for types used by a work package of the project	9 years ago
Alex Coles	df51b6ed99	Fix syntax (w/Rubocop) in (Rails) models ... Signed-off-by: Alex Coles <alex@alexbcoles.com>	10 years ago
Jens Ulferts	fdd3bd80b6	fix test_unit tests	10 years ago