51 Commits (45d1a0caa2dcd424d6f727f01f6a3fb610596805)

Author	SHA1	Message	Date
ulferts	cc4ed56e2a	use AR`s scope method instead of singleton class method (#8976) ... * use AR`s scope method instead of singleton class method By using the scope method, all of Rails` checks and method definition usually done on a method are now also performed on the extracted scope methods 5f3ff60084/activerecord/lib/active_record/scoping/named.rb (L154-L190) * turn scope classes into modules	4 years ago
ulferts	6140f4c7e9	update copyright to 2021 (#8925) ... Updates the copyright to 2021 for all files that have a copyright. Files in our source code without the copyright header still do not receive one automatically. Additionally, backlisted files are also excluded. Previously the copyright of chiliproject which references redmine stated a copyright of redmine up to and including 2017 which is not true for the code we have in here. Because of that I changed that to 2013	4 years ago
ulferts	bf9bc70bb1	fix grouping by cf while summing (#8881)	4 years ago
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
ulferts	33099d666c	use integer/float value for summing	5 years ago
ulferts	a0565b435e	fix cf sums integer overflow	5 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
ulferts	0b15db3c9a	rename fixed_version to version	5 years ago
ulferts	125d51c2b8	enable SortCriteria to handle sort bys Procs	5 years ago
ulferts	4002be7c58	adapt spec expectation	5 years ago
ulferts	d65cd0d211	reuse sql string	5 years ago
ulferts	3ed9e45a95	semver sorting/group_by for wp table	5 years ago
Oliver Günther	fa33b8c296	[32296] Also ensure versions are sorted by name ... If versions are not sorted by date, the default work_packages.id sort will break up grouped versions if they have no date. https://community.openproject.com/wp/32296	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	a6a4031aa2	[31667] Fix ambiguous reference to project_id when group/sort ... Properly reference project_id to avoid ambiguous references to project_id when grouping by project_id and sorting by priority https://community.openproject.com/wp/31667	5 years ago
ulferts	aa3698d061	fix summing custom fields on wp table ... Before the fix, string values where returned and then the `+` method was called which lead to the strings being concatenated. A subsequent call of `integer?` failed. The fix performs the aggregation in the database which is not only correct then but can also be carried out considerably faster. The drawback is, that the casting breaks the abstraction introduced by the cf strategies	5 years ago
ulferts	c83ba63640	Revert revert unwanted in dev branch ... This reverts commit b05a8f7b54. The release/10 branch received a revert that was applied after changes from dev unwillingly where merged into it. But when merging release/10.0 back into dev, that revert was also applied to dev where the changes are indeed wanted. So we revert the revert for dev.	5 years ago
Oliver Günther	b05a8f7b54	Revert "[31080] Trigger wpEvent after custom action"	5 years ago
ulferts	c4dc6e2c91	ensure sums are also sorted by group_by column	5 years ago
Oliver Günther	64e6fae1b8	[30442] Use formatted custom value in xls export ... This also fixes localized output of custom fields such as float https://community.openproject.com/wp/30442	5 years ago
Oliver Günther	731bbd4104	[30763] Use stable sort for manual position ... Only moved items are being sorted, to avoid sorting the entire page when that is not yet necessary. This is a design decision to ensure only the minimum number of positions are being assigned and helps when sorting a restricted set of work packages from a bigger set. To avoid having ambiguous sort results, ensure a second sort parameter by ID. https://community.openproject.com/wp/30763	5 years ago
Markus Kahl	cb6d28136d	allow editing estimated time for parents, show derived separately	5 years ago
Markus Kahl	530aa631d5	don't count children twice when summing estimated hours	5 years ago
Oliver Günther	7ac2805779	Save integer relative positions by computing spaces between	5 years ago
Henriette Dinger	1be834f382	Remove option to disable type highlighting in the WP table	6 years ago
Oliver Günther	595a664753	[29683] Fix order statements of CF list ... Custom fields of type list have been refactored quite some time ago to contain a reference to a `custom_option` in their `custom_value.value`. The sort statements still sort by the `custom_value.value` without joining properly, which results in sorting the internal IDs and not the correct positions. https://community.openproject.com/wp/29683	6 years ago
Oliver Günther	622e73664d	Remove hierarchy paths and migrate away from parent column	6 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	8ab4f2a663	Boards module (#7008) ... * Hack spike to show D&D use case [ci skip] * Add ordered work packages * Save order on existing work packages * Boards WIP * CDK drag * Add dragula handler [ci skip] * Add filter to return all manual sorted work packages * Print icon on hover * Boards routing and list components * Better loading indicator on list with streaming result [ci skip] * Add new board and list buttons [ci skip] * Post new query [ci skip] * Added creation of new board lists with persisted queries [ci skip] * Render placeholder row in empty queries [ci skip] * Push boards on grid * Use base class in scope [ci skip] * Extend api for options * Hack spike to show D&D use case [ci skip] * Add ordered work packages * Save order on existing work packages * Boards WIP * CDK drag * Add dragula handler [ci skip] * Add filter to return all manual sorted work packages * Print icon on hover * Boards routing and list components * Better loading indicator on list with streaming result [ci skip] * Add new board and list buttons [ci skip] * Post new query [ci skip] * Added creation of new board lists with persisted queries [ci skip] * Render placeholder row in empty queries [ci skip] * Save queries in grids [ci skip] * Renaming queries [ci skip] * Add existing work packages to board [ci skip] * Introduce card view component for work packages * Extend grids to allow project scope for boards (#7025) Extends the grid backend to also be able to handle boards. In particular, it adds the ability of boards to be attached to projects and changes the page property of grids to a scope property that better describes that more than one board can belong to the same scope (e.g. /projects/:project_id/boards). For a fully featured board, though, widgets need to be able to store options, so that they can store queries. Those widgets might also need to have custom processing and validation. That part has not been implemented. * introduce project association for boards * have dedicated grid registration classes * update and create form for board grids * extract defaults into grid registration [ci skip] * Add drag and drop to card view [ci skip] * Add options to grid * Fix option migration name * Renaming boards [ci skip] * Frontend deletion of boards * Avoid map on NodeList which doesnt exist [ci skip] * Add inline create to boards [ci skip] * Smaller create button [ci skip] * Add navigation for boards * Make inner grid same height * Replace index page with table * Workaround for widget registration [ci skip] * Fixed height for cards and tables [ci skip] * Implement escape as cancel d&d action [ci skip] * Fix and extend grid specs for name and options * Extend board specs for required name * Fix migration for MySQL references https://stackoverflow.com/a/45825566/420614 * Make board list extend from widget Since we cannot configure widgets yet, it's not yet possible to use a board-list widget anywhere. * Fix specs * Fix escape listener removal [ci skip] * Fix renamed to_path in relation spec [ci skip] * Allow deletion of grids for boards * Avoid reloading resource multiple times with replays * Frontend synchronization on deletion [ci skip] * Delete through table * Use work packages board path * Use work packages board path * Fix augmented columns breaking re-rendering * Fix duplicated permission with forums * Strengthen tab switch in specs * Add hidden flag for project-context queries Allows the API to create a hidden query that will not be rendered to the user even if it is within a project context. * private queries * Add hidden flag for project-context queries Allows the API to create a hidden query that will not be rendered to the user even if it is within a project context. * Move boards below work packages * Add Board configuration modal * Fix reloading with onPush * Saving / Switching of display mode [ci skip] * Extract wp-query-selectable-title into common component * Fix renaming of board-list * Fix auto-hide notifications in boards * Add permissions to seeders * Reorder lists in board * Linting * Remove default gravatar from settings * Show assignees avatar in the card view of WPs * Fix specs * Add missing method * Fix timeline icon * Use URL as input to be able to show avatars for groups, too * Fix test * Add further specs * Use correct data attribute to avoid unnecessary data base calls * Add further specs * Deletion of board lists * Pass permission via gon to decide whether we can create boards * Fix rename spec * Cherry-pick of 7873d59 and 30abc7f	6 years ago
Oliver Günther	1a8090402f	try to save highlighted attributes	6 years ago
Oliver Günther	6541cbe073	Add highlightable column	6 years ago
ulferts	5f8359a55c	when sorting by version, sort by name only (#6201) ... [ci skip]	7 years ago
Oliver Günther	6ef4211e77	Bump copyright to 2018 (#6171) ... [ci skip]	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
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
ulferts	587c3d6d40	fix poor mysql performance on sorting by parent (#6059) ... [ci skip]	7 years ago
ulferts	7d5616119f	replace dynamic AR method by static string (#6049) ... In cases where the filters are loaded before the migrations have run, the relations table might not exist. [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	4d95cc815f	Feature/guarded relation columns (#5784) ... * refactor case statement * guard relation columns by enterprise token [ci skip]	7 years ago
Oliver Günther	bbd10c8dfe	Review remarks	8 years ago
Oliver Günther	2c0ebf0a6e	Add relationType to relationOfType column ... So we can avoid matching the id/href in the frontend.	8 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