TOPIC: Fields with selection limit 1....

My issues are regarding custom fields:

In my setup I have created a field with a dropdown list and selection limit 1 and an associated price.
Each slot can be booked by one person only and should then not anymore be available for
selection.

1. ISSUE:
=========
I have registered as a single person for an event. Then I wanted to perform a change
on my registration via User Panel.

When I now open my event I can see all standard fields are filled with the values of my original
registration - but the field with the drop down list does say 'Select ...' while I would expect
to see the value that I have originally selected during initial registration.
But here I cannot see anything which makes me believe I have not booked anything.

Interestingly this works fine when I make a group booking.
Here I can go back to my registration and can see the original value

The same issue in backend:
While the administrator can see what the group members have selected, there is no value for the single booking.

As a user I would expect to see what I have selected perviously ....otherwise a change on a record
does not make sense when I do not know what has been selected/booked before.



In backend I have enabled
Listing Options:
Backend Members List
Frontend Attendees List


2.ISSUE:
=========

On same custom field with selection limit 1, I have another issue:

When I make a group booking, for every person I can select the same slot while it should be just 1.

This worked fine in 2.6.9 after long discussion in a support ticket - and slots that have been selected before were not selectable anymore.

Now with 2.7.0 (have tested every version up to 2.7.0h2), we are back to the issue I reported.

I would expect that doesn't matter whether it is an individual or a gropu booking, the
selection limit defined for the field would be taken into consideration in all possible
scenarios.
When one slot is selected it should either be removed for next booking or greyed out to be not
selectable anymore - otherwise it does not make sense to implement a functionality in DT Register
with selection limitations.

Any news on my threat ???