openproject

Commit Graph

Author	SHA1	Message	Date
ulferts	38d2707946	Fix/wp sums in db (#8580 ) * remove apparently unused methods * have specs for wp query sums * grouped sums in sql * sql for total sums * alter interface of all_grouped_sums Since we now fetch all sums in one sql statement it no longer makes sense to fetch the group sums individually * remove now unused method * extract method * Add material_costs to summing * add labor_costs to group sums * add overall costs to sum * fix sum grouping descision * fix summable? check * remove work_package_list_summable_columns setting Now all summable columns are always summed. The user no longer needs to select summing up in the settings. Selecting the column to be displayed and activiating sums will suffice * fix flickering spec	4 years ago
Oliver Günther	977deb4782	[32808] Allow null handling in custom fields based on direction Due to the way the order statements are constructed, we cannot provide null handling from within `order_statements.rb`, since the direction is append behind it, and null handling in postgres needs to be behind the direction. Thus we can provide a null handling that is based on the direction only https://community.openproject.com/wp/32808	5 years ago
Oliver Günther	f4f1e98b20	[32156] Use backlogs sorting of versions date for work packages - Adds a null_handling option to the property columns to allow `NULLS FIRST/LAST` to be handled - Adds a query specific SortCriteria that can work with null_handling - Fixes sorting of allowed_versions to reuse that sort order https://community.openproject.com/wp/32156	5 years ago
Henriette Dinger	bd7f4e4814	Update copyright notice	5 years ago
Oliver Günther	1cd325bd5a	Ensure sql join in manual filter and sort column is isolated in query We depend on ordered_work_packages association for determining sort and filter for manual sorting. We could restrict the join result with where(query_id: context.id) later but that prevents the execution planner from optimizing on the explicit join clause. This PR introduces a sql join that depends on the query_id and thus retrieves the correct order performantly.	6 years ago
Oliver Günther	6ef4211e77	Bump copyright to 2018 (#6171 ) [ci skip]	7 years ago
ulferts	a28ec25957	Fix/parent sorting missing elements (#6118 ) * Revert "remove unused sortable join (#6099)" This reverts commit `c1be19a6da`. * prevent descendant wps to not be present in filter result on parent sort On sorting by parent, we need to join the query with a subselect that returns only the topmost hierarchy relation (i.e. the relation that has the highest hierarchy value) per work package. Otherwise, if more than one row is returned per wp for the subquery, the work package is also counted multiple times against the provided limit which leads to less work packages being returned than expected. [ci skip]	7 years ago
ulferts	c1be19a6da	remove unused sortable join (#6099 ) [ci skip]	7 years ago
Oliver Günther	0d55bc0308	[26675] Remove implicit ID sorting on parent sort (#6039 ) * [26675] Remove implicit ID sorting on parent sort https://community.openproject.com/wp/26675 * parent sort -> breadth first sort, top down [ci skip]	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	55695ed756	adds query columns by relation type (#5625 ) [ci skip]	8 years ago
ulferts	ace7098eb3	add relations columns to query (#5606 ) * add relations columns to query * refactory query columns * rename QueryColumn to QueryColumn::Property QueryColumn is now only an abstract supertype [ci skip]	8 years ago

13 Commits (ac12222556cae5a230332f2fe9808ef7c9bfaf5d)