https://community.openproject.org/work_packages/65866
Set journal timestamp method to explcitly pass utc string to the query.
This will force the UTC timezone to be applied on the date instead of
letting postgresql to decide on the timezone.
* aggregate journals on write - simple implementation
* remove references to aggregated journals on read
* rewrite existing journals to be aggregated
* remove aggregated journal reference
* only delete predecessor if it can be aggregated
* fix aggregation condition
* adapt specs
* remove aggregated journal functionality from production code
The code is still necessary in a migration for the time being
* adapt specs
* use polymorphic belongs_to for journal data
The association can then be employed for eager loading
* eager load for activity rendering
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
By forcing the caller to disable mail sending via a block, we can also
ensure that the value is reset.
But by it, we can allso allow disabling mail sending for multiple
save_hook runs which was not possible before.
* use cte for aggregated journal
* Revert "use cte for aggregated journal"
This reverts commit 5fedefefdd.
* add another subselect that could later on be provided from the outside
* allow passing a nukleous sql to aggregated journals
* wip - using aggregated journal for activity
* new sql for aggregated journals
* start implementing new aggregated query
* additional documentation
* consolidate activity functionality
* simplify by turing into instance methods
* move activity fetcher out of redmine
* remove verb verification made obsolete
Without catchall routes, the dispatching handles it
* remove duplicate authorize check
* refactor activities controller
* refactory activity fetcher
* cache avatar file
* sort choosable events
* remove legacy spec covered by contemporary
* speed up aggregated journals via CTE
* instance var might never have been set
* ensure the event_types are always transmitted
* correctly reset the avatar cache
* fix avatar fetcher expectation regarding wiki pages
* adapt spec
[ci skip]
* map date name in changeset
* handle date switch in wp form
* Don't stub_const for services that may exist before hand
This will cause the const to be evaluated already, so that stub_const
has no effect there. This is why this fails depending on the order on
travis, but not locally/isolated.
[ci skip]
... instead of displaying the diff for the requested journal only
- this should provide the best forward compatibility of links
- even when aggregation timeframes are changed intermittently
as-op