Inappropriate options offered when requesting more than one session through secr/sreq

[jennifer-richards]

Describe the issue

@flynnliz reports:

I was just editing a session request when I noticed that something isn’t quite right on /secr/sreq. When a WG requests two sessions, it seems like they are exposed to many more scheduling options on the second one than they are in the first.

Here’s a screenshot of what I saw in RTGWG’s request:

Session 1 looks as expected, with only a Purpose of “Regular” available in the dropdown.

Session 2 includes the Name field. The first dropdown after Purpose only lists “Regular,” but the second dropdown lists the full range of session type options (regular, break, registration, etc.)

Code of Conduct

• I agree to follow the IETF's Code of Conduct