Change Details

//As a member of the Campaigns team, I want to add timestamps to the ce_organizers table, so that we have logging for organizer actions/activities later. // **Acceptance Criteria:** * Add timestamps for the ce_organizers table, like: ** created_at ** updated_at ** deleted_at We'll do this for V1, even if we don't need that information, so that it's still available for past events. No need for backwards-compatibility and the beta DB can be backfilled with random dates. ==== Rough plan ==== - Create the columns on beta with a default random value - Create columns in the code with logic to populate them - (Wait for patch to reach beta) - Drop defaults on beta

//As a member of the Campaigns team, I want to add timestamps to the ce_organizers table, so that we have logging for organizer actions/activities later. // **Acceptance Criteria:** * Add timestamps for the ce_organizers table, like: ** created_at ** updated_at ** deleted_at We'll do this for V1, even if we don't need that information, so that it's still available for past events. No need for backwards-compatibility and the beta DB can be backfilled with random dates. ==== Rough plan ==== - Write the patch that creates the columns in the code, with logic to populate them. Review it, but **DO NOT MERGE IT**. Only give it a +1, **explicitly** writing in a comment that the +1 means you are approving the change (and not that you have a [[https://bash.toolforge.org/quip/AU7VVae36snAnmqnK_xL | working mouse ]]). - Create the columns on beta with a default random value - Merge the patch and wait for it to reach beta - Drop defaults on beta

//As a member of the Campaigns team, I want to add timestamps to the ce_organizers table, so that we have logging for organizer actions/activities later. // **Acceptance Criteria:** * Add timestamps for the ce_organizers table, like: ** created_at ** updated_at ** deleted_at We'll do this for V1, even if we don't need that information, so that it's still available for past events. No need for backwards-compatibility and the beta DB can be backfilled with random dates. ==== Rough plan ==== - Create the columns on beta with a default random valueWrite the patch that creates the columns in the code, with logic to populate them. Review it, but **DO NOT MERGE IT**. Only give it a +1, **explicitly** writing in a comment that the +1 means you are approving the change (and not that you have a [[https://bash.toolforge.org/quip/AU7VVae36snAnmqnK_xL | working mouse ]]). - Create the columns in the codeon beta with logic to populate thema default random value - (Wait for- Merge the patch and wait for it to reach beta) - Drop defaults on beta