Issue Summary

When a custom field is loaded into a Plan, it may have a "Default Value" option as set in the Custom Field configuration https://support.atlassian.com/jira-cloud-administration/docs/configure-a-custom-field/ 

Plans does not appear to respect this default value and will leave the field as blank when a new work item is created.

This is especially noticeable if this field is marked as Required, as it will cause saving changes back to Jira to fail for these work items. The user must then open the Unsaved Changes modal which will trigger a Global Work Item Create modal which does respect this default value, then hit Create on that modal for each work item affected in this way.

Steps to Reproduce

1. Have a Custom field with a default value via this configuration https://support.atlassian.com/jira-cloud-administration/docs/configure-a-custom-field/ 
2. Make the field required https://support.atlassian.com/jira-cloud-administration/docs/specify-field-behavior/ 
3. Optionally, have the Custom Field on the Layout of the work item type you're going to create
4. Create a plan
5. Add this custom field to the plan
6. Add this custom field to the list of fields in the Timeline view
7. Create a new work item of that work item type
8. Observe that the custom field has no value associated with it
9. Open the Unsaved changes modal and try to save the work item
10. Observe that a flag appears saying that the creation failed
11. Open the Unsaved changes modal and see that the Global Work Item Create modal appears
    1. If you added the field to the layout, you'll see the default value respected in the field here
12. Hit "Create" which will allow creation of the work item without any issues despite the "Work item can't be saved, Required fields must be added, or changed to optional to resolve" error.

Expected Results

Plans should respect the Default Value of a field when creating a new scenario Work Item OR at save time Plans should autofill this default value if there isn't one.

Actual Results

When creating a new scenario work item, the field is empty. When submitting the change when the field is required, Global Work Item Create appears, but it can be submitted with no changes to the field values.

Workaround

There are a few workarounds:

• Global Work Item Create can still be submitted per created work item.
• Ensure that the required field is filled in before it is submitted for saving back to Jira