842 Commits (79e27e79f472aafb9c639c9c0962d91f913df7cc)

Author	SHA1	Message	Date
Jens Ulferts	224c1d9c2b	squash migrations	7 years ago
Jens Ulferts	cf35cc65ad	squash all migrations up to 7.1.0	7 years ago
Jens Ulferts	c7a7198935	squash migrations	7 years ago
ulferts	5177c418c4	use integer for foreign key type (#11) ... [ci skip]	7 years ago
ulferts	0ede06e09c	use integer for primary key columns (#6217) ... Rails 5.1 uses bigint(20) as the default for primary key columns (id typically) when it used to be int(11) up until Rails 5.0. While it might make sense to change to bigint in the long run, we can not do this by altering the old migrations as existing installations would not profit from the change. We therefore force using int(11) for all old, and potentially already executed, migrations. [ci skip]	7 years ago
ulferts	eaf0eb6be9	Feature/bump rails to 5 1 (#10) ... * declare rails version in migrations * specify type on foreign key [ci skip]	7 years ago
Jens Ulferts	ff7f501856	ensure 5.1 compatible migrations	7 years ago
Markus Kahl	0d3a197566	deserialise possible values if they are still a string ... coming from old data	7 years ago
Markus Kahl	8a067571c1	migrating from old data the fields may be empty strings ... which cannot be deserialised into arrays	7 years ago
Markus Kahl	c384998047	use separate custom field class not to use new code ... otherwise #default_value will fail at this point	7 years ago
Markus Kahl	def0b19e5a	project and versions attachments fix	7 years ago
Markus Kahl	02918c50e4	impossible values nil fix	7 years ago
Jens Ulferts	947401c5cb	declare rails version in migrations	7 years ago
Jens Ulferts	58e50ab5b0	declare rails version in migrations	7 years ago
Jens Ulferts	43da475f8c	declare rails version in migrations	7 years ago
Jens Ulferts	3644255cd6	declare rails version in migrations	7 years ago
Jens Ulferts	b1ab6a6dff	declare rails version in migrations	7 years ago
Jens Ulferts	5e875c9b73	declare rails version in migrations	7 years ago
Jens Ulferts	8632be1998	declare rails version in migrations	7 years ago
Jens Ulferts	57ce79e541	declare rails version in migrations	7 years ago
Jens Ulferts	95a4c352d7	allow sorting custom actions	7 years ago
Jens Ulferts	9bf5d05fdb	add description on custom action ... * turn custom action into fully fledged resource * add description to custom action model * load custom action resource on mouse over and display in title	7 years ago
Jens Ulferts	ed963003ef	propose pgsql 9.5 instead of 9.6	7 years ago
Wieland Lindenthal	546143e8ec	DRY migration	7 years ago
Wieland Lindenthal	c8d610e2ba	Satisfy rubucop	7 years ago
Wieland Lindenthal	b8c2752551	remove structure.sql from version control	7 years ago
Wieland Lindenthal	0a21541dd7	Allow filter WPs based on the content or file name of their attachments	7 years ago
Wieland Lindenthal	f2ebad3915	WIP: attachment search	7 years ago
Oliver Günther	6ef4211e77	Bump copyright to 2018 (#6171) ... [ci skip]	7 years ago
ulferts	8e7c23c832	add message to dag rebuilding (#6163) ... [ci skip]	7 years ago
Jens Ulferts	ab22a7fa97	add project condition	7 years ago
Jens Ulferts	75ce761cdb	add type condition	7 years ago
Jens Ulferts	d20960b998	add role condition	7 years ago
Jens Ulferts	886273ee86	initial implementation of conditions - status	7 years ago
Jens Ulferts	73d55f9e43	wip	7 years ago
Oliver Günther	57d315d733	Hotfix: Increase max iterations for rebuild_dag! ... [ci skip]	7 years ago
Oliver Günther	309e966418	Implement member-based synchronized groups	7 years ago
ulferts	8c732b9a42	Fix/parent depth first sorting (#6133) ... * maintain hierarchy path for performant sorting * by default - only sort by parent Parent sorting is exclusive as the sorting used is depth first. Because of that, the id of the work package is always part of the parent order criteria. By that, all other properties of the work package become irrelevant. [ci skip]	7 years ago
Jens Ulferts	7900a45b30	remove potential duplicates before unique index	7 years ago
Jens Ulferts	baa7e99d1d	cleanup timelines data	7 years ago
Jens Ulferts	35da4bac4d	speedup scheduling	7 years ago
Jens Ulferts	dd9d9b27e9	squash transitive relations	7 years ago
Markus Kahl	e8ac75b1a1	Outgoing webhooks ... Adds outgoing webhooks for work package events. https://community.openproject.com/projects/openproject/work_packages/24832/activity	7 years ago
Oliver Günther	b298b70737	Remove warning in migration ... [ci skip]	7 years ago
ulferts	1cc9601d30	Fix/circular dependency error handling (#6040) ... * recreation of reflexive relations is handled by gem * bump typed_dag * adapt method name as typo was fixed in gem * provide l10n for circular relationships * avoid overriding method [ci skip]	7 years ago
Oliver Günther	6443c55071	Use HashedToken from core	7 years ago
Oliver Günther	1f2492bb8b	Implement HashedToken (ExtendedToken from MOTP) in Core	7 years ago
Oliver Günther	fe6860b38a	Add development seeder (#5334) ... [ci skip]	7 years ago
Oliver Günther	3430661be5	Initial commit of 2FA plugin forked from MOTP	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