Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

requests for regular sessions shouldn't offer name (or type of timeslot to map into). #3531

Closed
ietf-svn-bot opened this issue Jan 31, 2022 · 4 comments
Closed

requests for regular sessions shouldn't offer name (or type of timeslot to map into). #3531

ietf-svn-bot opened this issue Jan 31, 2022 · 4 comments
Labels
component: meeting/ major

Comments

@ietf-svn-bot
Copy link

resolution_fixed type_defect | by rjsparks@nostrum.com

The secr/sreq form is offering fields for normal sessions that should not be offered.

Chairs shouldn't be able to give a Regular session a name, nor select the timeslot types it might land in.

Issue migrated from trac:3531 at 2022-03-04 09:26:35 +0000
@ietf-svn-bot
Copy link
Author

@jennifer@painless-security.com changed status from new to closed

@ietf-svn-bot
Copy link
Author

@jennifer@painless-security.com set resolution to fixed

@ietf-svn-bot
Copy link
Author

@jennifer@painless-security.com commented

Fixed in 5f9868e:

Fix hiding of name/purpose/type fields when not needed in secr/sreq. Fixes #3531. Commit ready for merge.

@ietf-svn-bot
Copy link
Author

@rjsparks@nostrum.com commented

Fixed in 75634e6:

Merged in 5f9868e from jennifer@painless-security.com:
Fix hiding of name/purpose/type fields when not needed in secr/sreq. Fixes #3531.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
component: meeting/ major
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ietf-svn-bot