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

Multiple Offerings Event Name #1331

Open
hoerstl opened this issue Sep 4, 2024 · 2 comments
Open

Multiple Offerings Event Name #1331

hoerstl opened this issue Sep 4, 2024 · 2 comments

Comments

@hoerstl
Copy link
Contributor

hoerstl commented Sep 4, 2024

When we create an event and give it multiple offerings, we gain the ability to give each offering a unique name. When we do this though, every event we create has a name and the original name for the event becomes irrelevant yet is still required for the form to be saved.

image

The now irrelevant event name is not used anywhere else (to my knowledge) yet remains a required field meaning that if you simply click the toggle to offer multiple events, you're forced to manually enter dummy name data before you can create all the events. This should not be the case.

Since this is a UI decision, we should talk this over with Brian.

@hoerstl
Copy link
Contributor Author

hoerstl commented Sep 4, 2024

asdfs

@vungc
Copy link
Contributor

vungc commented Dec 5, 2024

This issue is modified in PR #1349, Multiple Offerings and Repeating Events Refactor with the input box being greyed out when the series toggle is toggled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants