mirror of
https://github.com/stablyai/orca.git
synced 2026-10-28 08:02:54 +00:00
Neil
3ffbaf2e61
Jira's create-issue dialog rendered user fields (e.g. Reporter, schema
type "user") as a plain text Input and submitted the raw string. Jira
Cloud v3 requires the { id: accountId } object shape (display names and
usernames were removed in the 2019 GDPR change), so any required user
field rejected the create with "Reporter is required".
This adds schema-driven user-picker support end to end:
- buildJiraCreateFieldValue now maps user-picker drafts to { id } (single)
or [{ id }, ...] (multi-user array), extracted alongside the rest of the
create-field value logic into jira-create-field-value.ts so it is unit
testable.
- A searchable JiraCreateUserPicker combobox replaces the text Input for
user fields, backed by a new project-scoped search
(listAssignableUsersForCreate -> /user/assignable/multiProjectSearch with
a /user/search fallback) wired through IPC, the runtime RPC registry, and
the runtime-jira-client wrapper so it works over SSH/remote runtimes.
- Required user fields default to the connected site's token owner so the
dialog submits with zero interaction.
Detection is generic (schema type/items/custom), so assignee and custom
user-pickers work too, not just Reporter.
Fixes #4643