Forge UI Kit Select may incorrectly deduplicate, consume, or serialize shared option-object references when the same options array is passed to multiple sibling Select components

Issue 1: Multi-select value is not rendered after selection

The Work Type options are loaded and displayed correctly. However, after selecting an option, the selected item immediately disappears.

Possible reason:

This appears to be a Forge UI Kit reconciliation or serialization issue affecting controlled multi-select values, rather than an application data issue.

Issue 2: The second Select receives no options when sharing an options array

Start State and End State used the same statusOptions array. Start Rule and End Rule similarly shared the same triggerOptions array:

<Select options={statusOptions} /> // Start State
<Select options={statusOptions} /> // End State

Browser DOM inspection confirmed:

  • Start State displayed all 7 expected options.

  • End State displayed No options.

  • Start Rule displayed all 4 expected options.

  • End Rule displayed No options.

The underlying arrays were populated correctly. The failure consistently affected the second sibling Select receiving the same array and option-object references.

Related Ticket: Jira Service Management