Redmine

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.