Skip to content

Set timestamps correctly when propagating

What does this MR do and why?

When bulk creating or bulk updating integrations, we were previously copying the inherited integrations created_at and updated_at timestamps overtop of the group or project-level integration's timestamps. And similarly for the data fields.

Changes:

  • When bulk creating, set created_at and updated_at to current time.
  • When bulk updating, set only the updated_at to current time (and not change the existing created_at value).

Refactors:

  • (#to_database_hash) for data fields moved to BaseDataFields
  • ZentaoTrackerData to include BaseDataFields

Related to #360898 (closed)

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Luke Duncalfe

Merge request reports