Files
orca/src/preload
Brennan Benson 44f0fc09b4 fix(jira): scope the user-field rewrite to declared fields and decode search rows
Two review threads on #17090.

The {accountId} marker is a shape, not a type, so createIssue rewrote any
customFields value that merely looked like a user. The renderer already knows
Jira's verdict — schema.type 'user', or an array of them — so it now sends that
key list and the host rewrites only those keys. A key it was not told about is
unknown, and unknown is left exactly as it arrived.

normalizeJiraUserSearchResult cast each users entry to JiraUser without checking
it, so a row with no accountId or displayName reached the picker, which keys and
labels rows by both. Each entry is decoded now; one unreadable row fails the whole
search into the unexpected-response path this PR already built, because a filtered
list would look like the site's full answer.

Moved the Jira IPC argument normalization into its own module to stay under the
300-line cap without a suppression.
2026-08-29 18:57:56 -07:00
..