Default Value on Edit Screen or Transition Screen NOT working

Issue Summary

When Creating a Custom field, with 2 or more Configuration Contexts, in which have different Default Values.

If there are issues, which have no value in this custom field, when showing the Edit Screen or the Transition Screen, It shows the first value of the list and does not show the default value as mentioned in the configuration context.

This is reproducible on Data Center: yes

Steps to Reproduce

1. Create a Custom field "select list (single Option)"
2. Add 2 values (yes and No)
3. Create 2 configuration contexts, one for Default yes and one for Default no
4. Assign Configuration Context Default Yes to Project A
5. Assign Configuration Context Default No to Project B.

if You add to all screens:

• On Create Screen: It will work as expected
• On Edit Screen: (on old issues) that do not have a value assigned to this custom field, the Configuration Context is not respected.
• On Transition Screen: (on old issues) that do not have a value assigned to this custom field, the Configuration Context is not respected.
• This will happen for tickets that are not asking for this value when create and only ask for this custom value for any transition screen.

Expected Results

When an Issue does not have a value assigned to this custom field, it should show the value configured as default, so this can be saved.

Actual Results

The custom field is showing the first value of the List.

Workaround

Make sure that the value you want to have as Default is the first on the list of options. It will be used as default then.