Defect #43904
open
Activities of TimeEntries are not updated when moving the TimeEntry to a different project
Description
TimeEntryActivities can be derived in a project. In the database, this results in a new row in the enumerations table with a project-specific TimeEntryActivity which references the global activity in the parent_id.
When moving time entries between projects, the activity of time entries is currently not updated. This can result in time entries erroneously referencing the previous derived activity from the prior project, or to erroneously reference a global activity ID rather than the derived activity from the new project.
When updating a TimeEntry, the referenced activity must be updated to the currect one of the target project. This must also be cleared for existing time entries in a one-time migration.
Files
Updated by Holger Just 7 months ago
- Subject changed from Activities of TimeEntries are not updaten when moving the TimeEntry to a different project to Activities of TimeEntries are not updated when moving the TimeEntry to a different project
Updated by Marius BĂLTEANU 4 months ago
- Target version changed from 7.0.0 to 7.1.0
Updated by Marius BĂLTEANU 4 days ago
- File 0001-Update-time-entry-activities-when-moving-issues-or-t.patch 0001-Update-time-entry-activities-when-moving-issues-or-t.patch added
I've written a patch to fix this issue. Beside the case when the TimeEntry is moved to a different project, I've covered another case when the issue with time entries is moved to another project.