NOTE: Removing a Jira field, pressing Save, then adding the Jira field back and pressing Save does NOT reflect the custom field that were previously created when attempt to "Create" a new Jira ticket. To resolve this you have manually add back the custom fields by going into the "Configure fields" and selecting the fields that you want visible.

The above suggestions may be correct with regard to the "Edit" screen. 

I would not describe this as a workaround, it is "the" fix. There is some missing background data in the broken issue types, updating again correctly recreates this data, so the problem should not re-occur on future issue type changes.

Anything that allowes you to click the "Save Changes" button (greyed out in the attached screen shot) will resolve the issue for that issue type.

@sam, my pleasure .

@Keynan, I'm not sure I correctly understand what you mean. Do you mean the bug has been fixed and we just need to do the workaround I described to clean up the data structure? Meaning that we will not face this issue anymore for new custom field. Or is this something else entirely?

The code has been repaired, however application state must be restored manually. Any modification to the settings of the effected issue type should restore normal functionality.

@David, that work around just worked for me. Thanks for sharing!

The following workaround works perfectly for me:

1. Open the Project settings in a next-gen Jira project.
2. Open Issue Types
3. Add a default Jira field to the issue type that has the custom field.
4. Click save.
5. Remove the same default Jira field from the same issue type.
6. Click save.
7. Now the custom field is visible in each product backlog item of the corresponding issue type .

Hope that helps the community.

Let's get this soaked already, how long can you guys stall this major fix.

@Keynan, what does awaiting soak mean? When do you expect this issue to be resolved?

Thank you. 

We are experiencing this issue as well.

I am also experiencing this issue as well. 
Custom Field added does not display when creating a new issue regardless of the issue type (Epic, Bug, Story).

The Workaround above does not work even after saving the issue type or adding an new custom field, or moving from primary to secondary fields.

This is a regression, I agree with @Sam Parkinson => This is now a critical issue. We also may not be able to adopt Next-gen Jira and may potentially look for alternatives to Jira if this is not resolved. 

Cc: Keynan Pratt.

Please inform us as soon as this is resolved. Thank you.