Problem Statement

Today, when form fields in IDP (Backstage/Jarvis forms) are pre-filled using ContextViewer / formContext data from API responses, any field defined as an enum (dropdown) is rendered as a read‑only text input, not as a selectable dropdown.

As a result:

Users can see the previously saved value

But cannot change it using a dropdown

They must manually type values, which leads to errors and poor UX

This behavior occurs even when:

The field is explicitly defined as an enum

The API response value matches one of the enum options

Current Limitation

ContextViewer + enum fields do not work together

Once a value is injected via form context:

Dropdown UI is lost

Field becomes a static input

Setting defaults via API or context overrides enum behavior entirely