In Progress
Since the ids are significant, when in the MIGRATION_WRITE_BOTH stage, the block should be written to the old schema first and then the insert id should be used for the bt_id and the be_id this should keep the block ids in sync between the old schema and the new schema until in the next phase of the migration. This should be done in a single transaction to ensure that the insertion happens as intended.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T366388 Multiblocks: Edit and Remove a block | |||
| Open | None | T349689 Admins should be able to edit an active block without needing to delete it first | |||
| Open | None | T204903 Epic ⚡️ unprioritized Partial Blocks features | |||
| Open | BUG REPORT | None | T25310 Global suppression does not work properly when the target has already been locally blocked | ||
| Open | None | T194697 Multiblocks — Allow for multiple, simultaneous blocks with different expiration dates | |||
| Declined | None | T202572 Create Migration Plan from current schema to Multi-block schema |
The development of this project would be a massive time and resource investment for minimal impact. Boldly closing.