diff --git a/server/migrations/248_issue_subscriber_delegated.down.sql b/server/migrations/249_issue_subscriber_delegated.down.sql similarity index 100% rename from server/migrations/248_issue_subscriber_delegated.down.sql rename to server/migrations/249_issue_subscriber_delegated.down.sql diff --git a/server/migrations/248_issue_subscriber_delegated.up.sql b/server/migrations/249_issue_subscriber_delegated.up.sql similarity index 100% rename from server/migrations/248_issue_subscriber_delegated.up.sql rename to server/migrations/249_issue_subscriber_delegated.up.sql diff --git a/server/migrations/249_issue_subscriber_opt_out_scope.down.sql b/server/migrations/250_issue_subscriber_opt_out_scope.down.sql similarity index 100% rename from server/migrations/249_issue_subscriber_opt_out_scope.down.sql rename to server/migrations/250_issue_subscriber_opt_out_scope.down.sql diff --git a/server/migrations/249_issue_subscriber_opt_out_scope.up.sql b/server/migrations/250_issue_subscriber_opt_out_scope.up.sql similarity index 87% rename from server/migrations/249_issue_subscriber_opt_out_scope.up.sql rename to server/migrations/250_issue_subscriber_opt_out_scope.up.sql index 1abe01ba08..39dbaedec6 100644 --- a/server/migrations/249_issue_subscriber_opt_out_scope.up.sql +++ b/server/migrations/250_issue_subscriber_opt_out_scope.up.sql @@ -1,6 +1,6 @@ -- MUL-5483 review follow-up: an opt-out has to remember HOW FAR it reaches. -- --- 248 gave every unsubscribe a tombstone, and HasAncestorOptOut treats any +-- 249 gave every unsubscribe a tombstone, and HasAncestorOptOut treats any -- ancestor tombstone as "do not re-subscribe below here". That made the two UI -- choices — "unsubscribe from this issue" and "…and its sub-issues" — differ -- only for descendants that already exist: both silently suppressed FUTURE @@ -11,7 +11,7 @@ ALTER TABLE issue_subscriber ADD COLUMN opt_out_scope TEXT CHECK (opt_out_scope IN ('issue', 'subtree')); --- Rows tombstoned by 248 predate the distinction. They were all written by a +-- Rows tombstoned by 249 predate the distinction. They were all written by a -- path that suppressed future children, so 'subtree' preserves their observed -- behavior rather than silently widening or narrowing it. UPDATE issue_subscriber SET opt_out_scope = 'subtree' WHERE unsubscribed_at IS NOT NULL;