Files
multica/server/migrations/134_issue_identifier_alias.down.sql
Naiyuan Qing fd2adbb9a3 feat(issues): support moving issues between teams with identifier aliases
Moving an issue renumbers it in the destination team (numbers are
per-team) inside one tx: allocate the next counter value, take a fresh
top position, and record the pre-move identifier in the new
issue_identifier_alias table. Both identifier resolution points (the
shared loadIssueForUser path and GitHub branch/PR auto-linking) fall
back to the alias, so old identifiers keep resolving forever; numbers
are never reused, so aliases can't shadow live issues.

Associations now bind at creation time only: drop the cross-team
parent/child checks, the explicit team x project association check in
ResolveTeam, the project-change team validation in UpdateIssue, and the
still-has-issues 409 when removing a team from a project. The broadcast
gains team_changed/prev_team_id.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-03 11:04:08 +08:00

2 lines
45 B
SQL

DROP TABLE IF EXISTS issue_identifier_alias;