issue-editing

Prevent stale updates by enforcing a fetch-before-edit workflow: call get_issue to retrieve the current state, validate entityType and field values, then check updatedAt timestamps to detect concurrent modifications before applying any mutations to issues.

Concurrent edit detection checks the updatedAt timestamp retrieved from get_issue. If the timestamp indicates a recent modification, the workflow surfaces the conflict and provides options to proceed with the edit, refetch the current state, or cancel the update entirely.

Yes, you can bulk update labels and assignees safely by first fetching the existing issue state, validating assignee identifiers and labels against platform-specific rules, and confirming the updatedAt timestamp has not changed since retrieval before applying the bulk edit mutation.

The best way to validate status transitions is to fetch the issue using get_issue, verify the entityType is exactly an issue, and check the intended status change against platform-specific rules and valid transition paths before executing the update mutation.

Issue edits fail with hallucinated identifiers because the workflow requires fetching the actual issue state first. Blocking edits of non-issue entities and validating assignee and field values against retrieved data prevents fabricated identifiers from being used in mutations.

Yes, you need to fetch an issue before editing its title or description. The fetch-before-edit enforcement requires calling get_issue to establish the authoritative base state, ensuring title and description edits do not accidentally overwrite concurrent modifications made by other users.