834 Commits (f652819e71c8330feba3cca4de026863b1fd323a)

Author	SHA1	Message	Date
Oliver Günther	e1a88a9a40	[34001] Ensure filters always receive the query context ... In the mentioned project, the query copy service fails to execute because a filter has lost its context right after `query.save`. There is a hook for `after_commit` which is not relevant here since we're in a transaction, but the context is lost regardless. Instead, we could ensure whenever accessing the filters, the context is set correctly. https://community.openproject.com/wp/34001	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	6826f90ee2	Feature/remove timelog (#8557) ... * rename costs, introduce budgets * move files from costs to budgets * rename cost_object to budget * remove unused code * move hook - should be turned into standard code in the long run * move type attributes change over to budgets * move patch to work_package proper * move budget menu item up * combine reporting, time and cost module * remove rails based time_entries & reports code * rename cost object filter * adapt menu spec expectations * use cost project module name in administration * include timeline labels in migration * properly place budget linking method * fix permitted params * remove outdated routing spec * adapt budget request specs * ensure order of descendent updates * remove outdated specs * fix checking for reporting to be enabled * fix displaying spent units * fix time entries activity event url * reenable current rate tab * fix path on budget page * allow bulk editing of budgets only in one project scenario * fix sanitizing reference in controller * include module required for format_date * fix reference to correct units from work package spent units * linting * remove outdated spec * remove outdated views and permission references * remove acts_as_event from time_entries There is no atom link for time entries * remove acts_as_event from projects There are no atom links for projects * introduce budget filter for cost reports * remove actions added to removed controller * move time entries to the costs module * factor in view_own permission when calculating time entry visibility * linting * move mounting of time entries * include budgets into api v3 documentation	4 years ago
bsatarnejad	3676ead9aa	Change how watchers data is returned to front-end, blocked users are not returned	4 years ago
ulferts	8cb7ed632a	remove watchers embedded in wp representer ... A client should not rely on embedding and our front end does not appear to	4 years ago
ulferts	655f021b92	add derived dates to the work package resource ... The derived dates are the minimum/maximum of the descendant's dates. As long as the work package is scheduled automatically, the derived and non derived dates should be equal althoug the derived dates will be null in case non descendants exists. But if the user decides to activate manual scheduling the dates can deviate. The derived dates can then help to display the deviation to the user. This commit however does not alter the front end. The dates are eager loaded on the work package index commit using the same mechanims already introduced for spent time. The patched cost attributes, which are also eager loaded, are now eager loaded in the core as well so the patch is removed. As those attributes are now part of the core (although in a different module) it no longer makes sense to rely on patching for this.	4 years ago
ulferts	a2a559e553	remove almost duplicate, but faulty, readonly check ... The writability of the status is already checked at the attribute level	4 years ago
Oliver Günther	2feaec1101	[33678] Priority needs to be a require field ... Priority was marked non-required for it to turn up in the attribute form configuration. But priority _is actually required_. This results in the frontend adding an optional placeholder `-` value, which makes the resource unsavable. This commit adds priority to the form, but keeps it required as it should be. https://community.openproject.com/wp/33678	4 years ago
Markus Kahl	9c4d4ebc46	added :schedule_manually attribute to work package	5 years ago
Markus Kahl	ebdd8e0d8a	minor refactoring	5 years ago
ulferts	c546241459	extract into patch	5 years ago
ulferts	801811c6c0	avoid n+1 query for bcf issues on work package list	5 years ago
ulferts	0b15db3c9a	rename fixed_version to version	5 years ago
ulferts	25348c3ec2	stub in specs	5 years ago
ulferts	9e2287bfcc	rename and inflect according to zeitwerk	5 years ago
Henriette Dinger	bd7f4e4814	Update copyright notice	5 years ago
Henriette Dinger	67dd3bcb46	Replace all occurrences of settings_project_path && make toolbar and menu title consistent	5 years ago
Henriette Dinger	cbc530ca9d	Move project_settings_path to ApplicationHelper to be globally available and start adapting tests to new structure	5 years ago
ulferts	6c4e572f4e	consolidate allowed_* logic in the wp contract	5 years ago
ulferts	0bc1fb094f	extract sharable code into module and superclass	5 years ago
ulferts	7cca2631b0	add projects create form end point to api	5 years ago
ulferts	e37974dbed	actually provide all relevant custom fields for performance hack ... Before, the last iteration on a project determined the custom fields that where hacked to be loaded in a project. That way, when the last project had e.g. no custom fields on a specific type, the custom fields would be missing for all evaluations later on, even though it might actually have custom fields defined for other types. As the results of the first call would be cached, this would then also affect later requests	5 years ago
ulferts	ad847a3892	add type attribute group attributes to cache key ... This is an attempt to fix cases where some custom fields are not displayed. I suspect this will not fix the bug in itself. But it might help to narrow down the problem by preventing the bug to also affect users who are not affected by the bug originally but only because the buggy result was cached for them.	5 years ago
ulferts	d5ee1a7d20	ensure order of cache key	5 years ago
ulferts	a9213a39cc	remove duplicate permissions	5 years ago
ulferts	c3c197bc24	attachments for custom_text widgets on dashboard	5 years ago
ulferts	a880c85a1d	partial caching for wp schema attribute groups	5 years ago
ulferts	9bee1887b8	use hack to preload project`s custom fields	5 years ago
ulferts	5ee801b549	cache roles for project	5 years ago
ulferts	0dcb1777d6	reduce db hits for wp schemas	5 years ago
ulferts	3be6e61b85	turn descriptions cacheable	5 years ago
Markus Kahl	cb6d28136d	allow editing estimated time for parents, show derived separately	5 years ago
ulferts	cc41884048	add schema to project api and complete project resource	5 years ago
ulferts	880120fe1b	fix unsetting date on milestone work packages	5 years ago
ulferts	7971a29a8b	don't cache the attribute_groups	6 years ago
ulferts	4ffa71e68d	include a relevant setting in the wp schema cache key	6 years ago
ulferts	a199c94a6a	have permission specific schema caching	6 years ago
ulferts	e8f2ad5516	reenable caching using standard methods	6 years ago
ulferts	9c3206220b	remove mysql specific code throughout the application	6 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
ulferts	41bb309094	disable wp schema caching until it is turned save for it again ... [ci skip]	6 years ago
Oliver Günther	f492113c94	[30275] Allow global type select, restrict available projects ... This allows to select all available types globally, and restrict the projects to the ones that have the type available. The same functionality applies to embedded tables, where a filter on a type will ensure that only the projects with the type selected will be returned. https://community.openproject.com/wp/30275	6 years ago
ulferts	1f537b20a2	avoid setting author outside of service	6 years ago
ulferts	6e5b81dc3f	add schema specific wp contract	6 years ago
ulferts	5b758c1419	differentiate between user and system set attributes	6 years ago
ulferts	a5defb73c5	add dedicated permission to regulate assigning a version	6 years ago
Oliver Günther	3f131c659c	[29487] Apply filter criteria to embedded table inline reference ... This applies all non-relation filters to the inline referencing functionality of embedded relation/child tables. https://community.openproject.com/wp/29487	6 years ago
ulferts	a93ecca5a8	Feature/members api show (#7308) ... * basic members collection response * complete member index end point * document versions#index * remove user association from members There is already a more generic principals association. Having both causes confusion and leads to duplicate loading of models * linting * remove disabled test * add members#show api end point * add project and principal to member representer * replace member.user reference with principal * use principal reference in project members association * modernize roles api * complete member representer rendering * replace remnants of user association * add member schema api endpoint * have dedicated available projects end point for versions * linting * limit roles to assignable ones in schema * rename member to membership in api * remove remnants of user in member * spec fixes * use available_projects endpoint in versions board * add eager loading to memberships#index * members create form api endpoint * ensure role exists for default assignment * extract switch for users/groups to work_packages representer * document membership create form * add l10n expected in specs * strengthen the usage of a delete base service * use base class for set attributes service * fix alias in service * add create endpoint to members api * document members create endpoint * linting * adapt to altered service signature * use default endpoint for wp#get * use CF infused representer [ci skip]	6 years ago
ulferts	8af3f78247	consider both directions for relates to candidates	6 years ago
Oliver Günther	9a7ff60976	Replace jquery-autocomplete in wp-relations-autocomplete	6 years ago