Yes, this is a problem.  Actually there are several problems with the User Account Profiles.

The "List" type field is broken and is causing multiple headaches for my clients. 

See:  Custom Profile Property

Be aware these issues also apply to Custom Profiles:

• Ticking the "Profile Required For Registration" box on the User Account Profile page under Site Settings does not work.  For Private registrations, new users are able to create new registrations without completing all of the "required" custom profile properties
• In the same vein, if a new registrant fills in one or two fields and then submits the new registration, it creates a Critical Error and sends it back to the home page.  The expected behavior is to remind new registrants that required fields were not filled in
• Once a new registrant completes the new registration, the form no longer redirects to a hidden webpage in the site

See support.dotnetnuke.com for a complete list of all issues relating to profile and registration.

My recommendation is to stay away from 6.2.+ upgrades if your site relies on custom profile properties and "list" types.  With any new major release, there will be issues.  However, there will be also casualties.  Already we've had a couple clients move away from DNN this past year due to these issues; which is sad because DNN is a good product when it works as expected.  We've been using DNN since 2006 and will continue to support it.

 

Has the issue with lists been fixed in 6.2.3? On my local installation, custom list in the profile work fine but on PowerDNN the list doesn't seem to fully work.

What I'm doing:
I create a custom list profile property under site settings and make it visible. If I check the user account -> manage profile tab, the list shows up and works fine.

My issue is with adding the custom list to the registration page. The problem is that under Site Settings -> User Account Settings, the custom list profile property won't show up in the intellisense when picking my registration fields and thus I can't save it. Do I need to change to comma-delimited list to get around this? I don't have this problem on my local installation for development and testing. Both my local installation and the PowerDNN installation are running 6.2.3.