Dashboardcliissue merge --into participation

issue merge --into participation

Category: preference
Confidence: 1.00
ID: 01a08aa5-a528-7edd-9e1a-4b30efc252ff
Project ID: c760f4f9-42b0-4ce0-b36d-6b8c38d770b2
Cross-project: No
Recalled in other projects: 0
Source session: 0iRbOD1VHj1PKYbvU
Created: 2026-09-10 09:28:26
Updated: 2026-09-10 09:28:26

Content

sentry issue merge --into <issue> must always include that issue in the merge and prefer it as the canonical parent, even when absent from positional arguments. Chose effectiveArgs = [...args, flags.into] plus numeric-ID deduplication over treating --into as ordering-only because a preferred parent cannot be outside the merge set; Sentry may still choose a larger group by event count.

Move to: