Release/2025.02.3 [dev] #1761
Closed
Release/2025.02.3 [dev] #1761
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Release/1.8.1
Release/1.9.0 [main]
Release/1.9.1 [main]
Release/1.9.2 [main]
Release 1.9.3 [Main]
Release/1.9.4 [main]
Release/1.9.5 [main]
Release 2025.01.0 [main]
Release/2025.01.1 [main]
Release/2025.01.2 [main]
release/2025.01.2 [dev]
Release/2025.01.3
Release/2025.02.0 [main]
Release/2025.02.1
) This PR fixes the following issues: - After adding a new activity to an applet, its entry to `applet_events` uses the old applet version number - Adding a new scheduled event for an activity/flow removes all its previous scheduled event(s). There can be only one "always available" event, whereas many scheduled events per activity/flow should be allowed - In the *notification_histories* table, the *is_deleted* column doesn't become `true` after removing the notification from the event - In the *reminder_histories* table, the *is_deleted* column doesn’t become `true` after removing the reminder from the event
…t_events (M2-8743) (#1749) This PR updates the query being used to find all the events linked to an applet when that applet is updated. This list of events is used as the base for which rows get inserted into `applet_events` whenever the applet version changes without changing any event versions. Previously, the query being used was excluding individual events by adding the condition `WHERE user_id = NULL`
Release/2025.02.2 [main]
) This PR fixes the following issues: - After adding a new activity to an applet, its entry to `applet_events` uses the old applet version number - Adding a new scheduled event for an activity/flow removes all its previous scheduled event(s). There can be only one "always available" event, whereas many scheduled events per activity/flow should be allowed - In the *notification_histories* table, the *is_deleted* column doesn't become `true` after removing the notification from the event - In the *reminder_histories* table, the *is_deleted* column doesn’t become `true` after removing the reminder from the event
This PR implements the following cleanup operations:
- Adds four new columns to the `events` table:
- `activity_id`: taken from the `activity_events` table
- `activity_flow_id`: taken from the `flow_events` table
- `user_id`: taken from the `user_events` table
- `event_type`: Enum with value `activity` or `flow`
- Removes the `periodicity_id` column from the `events` table
- Migrates all the data from the `activity_events`, `flow_events`, and `user_events` tables into the `events` table
- Drops the `activity_events`, `flow_events`, `user_events`, and `periodicity` tables
- Updates the API code to account for these changes, which mostly included rewriting queries to select only from the `events` table where multiple joins (and sometimes multiple queries) were previously being done
These changes are intended to be 100% backwards compatible and should introduce no new features from the client perspective
This PR restores the following tables that were previous removed as part of #1723: - activity_events - flow_events - user_events This restoration is optional and should only run if the tables are missing. So it should run on dev, but do nothing on UAT. The rest of the code remains unchanged, and this change is made on Jody's suggestion to split this across two releases. There will be a follow-up PR that drops these tables in about a week or so
…migration-hotfix chore: Schedules database clean up + restore *_event tables (M2-8495)
* fix: displays translated subscale q/a in dataviz and data export Updates the script to update the subscale items in activity_items_histories, which is where the BE sources the submissions from for the dataviz and data export * fix: ruff formatting errors * fix: use date when ordering instead Original ordering by id_version works up to 1.9.0 but because it orders by text it incorrectly orders that higher than 1.10.0 * chore: Add logging --------- Co-authored-by: Marty <[email protected]>
|
➡️ Preview environment created: Click Me! |
|
❌ E2E tests failed |
ChaconC
approved these changes
Feb 27, 2025
Co-authored-by: Marty <[email protected]>
…lumn (#1766) Co-authored-by: Marty <[email protected]>
|
Abandoning this PR. Will branch from |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Merge
release/2025.02.3to dev