4 Commits (1c373bd1ff706492e5db4ad0c9371763127560c8)

Author	SHA1	Message	Date
ulferts	1bdd2ab9ae	safe automatic fixes by rubocop (#8994)	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
Jens Ulferts	30e398a35f	explicitly cast to arel instead of relying on delegation	6 years ago
Oliver Günther	5b49b33b21	Prepare for core integration	6 years ago
Jens Ulferts	6aa7fc5566	fix calculating spent time, labor/material costs when more than one value is present	8 years ago
Jens Ulferts	5a507c1283	fix eager loading time entries in the wp collection representer	8 years ago
Oliver Günther	5f831769a2	Use core time_entries sum query in work packages collection ... Due to the double join on time_entries, entries on a work package were doubled regardless of how the core aliases the table. Since the core does a join on time_entries anyway, costs can re-use that query for the labor_costs attribute on the WP collection representer.	8 years ago
Jens Ulferts	2758e52a85	use joins instead of subselects for eager loaded costs	8 years ago
Markus Kahl	693aff4b8d	prevent n+1 cost queries	8 years ago