Issue Summary

When a new context is applied to a custom field in Jira, existing values in Jira issue form lose their visibility in the UI. The field references the old values in the backend, but they are not displayed due to mismatched option IDs in the new context.

Steps to Reproduce

1. Create a custom field (e.g., formcf) of type Checkboxes.
2. Add the following options: ABC, DEF, GHI.
3. Associate the custom field with a form and link it to a project.
4. Create a ticket using the form and select the option ABC.
5. Introduce a new context for the custom field.
6. Define the following new options for the new context:
   • ABC, DEF, GHI, JKL, MNO, PQR.
7. Open the previously created Jira issue.

Expected Results

The previously selected option (ABC) should remain visible in the issue's UI, reflecting the values from the original configuration scheme.

Actual Results

• The selected option (ABC) is not visible in the UI.
• Using the API or database queries reveals that the issue still holds the old value from the original configuration scheme.
• The field attempts to load data from the new context, but the options do not align due to mismatched IDs between the old and new contexts.

Workaround

Manually edit the Jira form and update the value.