Issue Summary

If a Project is initially mapped to a context that has a default value assigned to it, and later on, the context for that Project is changed with different default value, it is essential that for any open issues associated with that Project, the default value is updated accordingly.
This update ensures that the default value accurately reflects the new context's default value, thereby maintaining consistency and ensure that all open issues are aligned with the most current context.

Steps to Reproduce

1. Create a custom field eg-(Select list - cascading) with a global context and default value.
2. Create an issues and don't select any value for the respective custom field.
   1. The issue gets created and default value get's assigned to the custom field.
3. Next, create a new context and map it to the project under which the issue was created in step 2. 
   1. Also create a new default value under this project.

The behaviour observed is that the issue created in step 2 is still mapped to the default value from older context.

Expected Results

The default value on the existing issues should update reflecting the default value from new context in case the Project context changes.

Actual Results

The default value on the existing issues does not get updated.

Workaround

Required, if there is no workaround please state:
Update the default values on the issues manually.