issue-fields-migration

# Issue Fields Migration [Issue fields](https://github.blog/changelog/2026-03-12-issue-fields-structured-issue-metadata-is-in-public-preview/) are org-level typed metadata (single select, text, number, date) that replace label-based workarounds with structured, searchable, cross-repo fields. Every organization gets `Priority`, `Effort`, `Start date`, and `Target date` preconfigured, with support for up to 25 custom fields. This skill bulk-migrates existing metadata into issue fields from two sources: - **Repo labels**: Convert labels like `p0`, `p1`, `priority/high` into structured issue field values (e.g. the Priority field). Supports migrating multiple labels at once and optionally removing them after migration. - **Project V2 fields**: Copy field values (single select, text, number, date, iteration) from a GitHub Project into the equivalent org-level issue fields. ## When to Use - User added org-level issue fields that overlap with existing project fields - User wants to copy values from project fields to issue fields before deleting the old project fields - User asks about "migrating", "transferring", or "copying" project field data to issue fields - User wants to convert repo labels (e.g., p0, p1, p2, p3) into issue field values (e.g., Priority field) - User asks about replacing labels with issue fields or cleaning up labels after adopting issue fields ## Prerequisites - The target org must have issue fields enabled - The issue fields must already exist at the org...