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!

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.

We were having the same issues as well.

https://community.atlassian.com/t5/Jira-Software-questions/Custom-Fields-in-Next-Gen-Project-Aren-t-Displaying/qaq-p/939009#M36362

I am also experiencing this issue. The workaround only half worked for me, fixing it for one issue type, but not for another.

This is going to cause an impact to my use of the nex-gen project board very shortly.

It seems to me this is a regression as it was working fine a week or two ago.

Here is my current situation:

1. I created a next-gen Jira project two weeks ago.
2. I created custom issue type with custom fields.
3. I have created product backlog items with the custom issue type for two weeks and I was able to access the custom fields.
4. Today, I created a new custom issue type using the same custom fields.
5. I created a product backlog item with the new custom issue type and I was unable to access the custom fields.
6. I created a product backlog item with the old custom issue type and I was able to access the custom fields.

So it seems that the problem might be with new custom issue type using custom fields.

I tested the workaround and the bug is still there. Awaiting for the final solution but I had to suggest not to use Next-Gen projects until this is fixed.

Hey paul.steckler, We've managed to find consistent steps to reproduce the issue and we're working on a solution. We hope to get it shipped soon. Thanks for your patience!

Hey folks, still waiting? No updates in the last 24 hours. 5 days and counting with no solution?

Hello ?!? Any updates? 

3 days and we are still broken and no updates for 24 hours?

Hey folks, any updates? I'd take any workaround at this point - we are essentially down at this point.

Testing this more:

1. Repros in one project for sure, BLUE
2. In another project this does not repro if I remove/add field
3. In a new project things appear to work

Unfortunately BLUE is mission critical for our team.

I also tried removing a custom field, City, saving, then adding it back. No change in behavior, it is still broken.

100% repros

If I remove and add the fields does this affect the data? We have made heavy use of this feature.

Also please don't lower the priority, this is crushing our business right now.

paul.steckler can you confirm if this problem is still occurring on your instance, can you try removing and re-adding the custom fields to your affected Issue Types?

We have been unable to re-produce this so far, we apologise for the inconvenience caused and suspect some caching issues at this stage.

Cheers,
Dylan - Service Enablement

Hi Jira - this is a mission critical bug for us and is blocking the team. Unsure what each priority means but Medium seems low.