114 Commits (60672eea1e6969c8eee0f8e9e89c9421cd97e220)

Author	SHA1	Message	Date
ulferts	94cc3fc188	ensure method exists	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	125d51c2b8	enable SortCriteria to handle sort bys Procs	5 years ago
ulferts	3ed9e45a95	semver sorting/group_by for wp table	5 years ago
ulferts	9e2287bfcc	rename and inflect according to zeitwerk	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
ulferts	c2311df6f5	avoid unsafe sql warning	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	c47a8bb5b0	fix group_by associated resource if only a nil group exists	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	a2fd8d7c40	Fix previous specs	5 years ago
Oliver Günther	7ac2805779	Save integer relative positions by computing spaces between	5 years ago
Oliver Günther	4ba8cf0ad4	Allow at max 250 elements to be rendered with manual sorting ... This hides the pagination and always returns a single page of at max 250 work packages for manual sorting	5 years ago
ulferts	5edb64b2df	use default filter behaviour for wps available for relations ... That way, we can treat the end point as just another wp endpoint with filter capabilities. Currently, there is a couple of custom logic still present but that is only due to wanting to not break the public API. In the long run, the whole end point could be removed as the same filtering is now available using /api/v3/work_packages with an appropriate filter.	6 years ago
Oliver Günther	80dfe61339	Make autozoom a regular zoom level option	6 years ago
Oliver Günther	9020120e44	[29689] Allow setting the sort dir for group_by column ... https://community.openproject.com/wp/29689	6 years ago
Jens Ulferts	17023c9394	optimize search filter by moving condition to join criteria	6 years ago
Oliver Günther	c6538c5b69	[29598] Fix SQL joins from filter when grouping ... https://community.openproject.com/wp/29598	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	ae8db4011a	Fix more deprecations	6 years ago
Oliver Günther	f86abae9eb	Enforce Arel.sql for string order, pluck	6 years ago
Markus Kahl	bdefaadf5e	fixed typo	6 years ago
Wieland Lindenthal	1dcb43623e	Add more highlighting specs for api v3	6 years ago
Wieland Lindenthal	b7414c4cc2	Improve Codeclimate	6 years ago
Wieland Lindenthal	07d9e7a6e1	Very basic settings for default highlighting	6 years ago
Wieland Lindenthal	f34018f482	Make highlighted_attributes be part of `valid_subset!` of query so erroneous saved queries will not fail, but saving them does. ... Further: - Ensure `to_sym` on attrbute reader - Improve validation error message by telling which attribute is making problems.	6 years ago
Wieland Lindenthal	0d3c109db7	Fix saving of queries with highlighted attributes. ... - Use column IDs instead of their href. - Fix validation. validates_inclusion_of was not doing the job as does not check for intersection - Extend parameter parsing for hightlighted_attributes - Extend contract	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
Jens Ulferts	43e293178c	avoid AR exception on overlapping groups	6 years ago
Oliver Günther	ec247a60a7	Add type to entire-row	6 years ago
Markus Kahl	3d8dea96ea	added wp list highlighting mode setting	6 years ago
Oliver Günther	d48f67688f	Also revert to none in backend, otherwise this will break specs	6 years ago
Oliver Günther	f3e2100247	Save highlighting mode to query	6 years ago
Oliver Günther	33944345f3	Implement mode switching in display settings	7 years ago
Oliver Günther	1701750dda	Implement tab portal outlet with multiple attached views	7 years ago
Wieland Lindenthal	1e468b3cbf	more rubocop stuff	7 years ago
Wieland Lindenthal	503502fa12	rubocop stuff and cleaning up code	7 years ago
Wieland Lindenthal	6dc3a11a65	Satisfy or calm rubocop	7 years ago
Wieland Lindenthal	aa0f70681b	Add first LIKE based WP filter for Attachment content and file name	7 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
ulferts	7d30fcbc8e	allow AR to alias on distinct (#6106) ... When passing a string to #order AR has no chance to alias columns. This can clash when two columns from different tables having the same name are part of the query (e.g. id). By providing an array, AR applies aliases to columns it needs to have in the projection on SELECT DISTINCT ... ORDER BY statements. [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