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

Reevaluation on End Date field. #1348

Open
ojmakinde opened this issue Oct 10, 2024 · 0 comments
Open

Reevaluation on End Date field. #1348

ojmakinde opened this issue Oct 10, 2024 · 0 comments
Assignees

Comments

@ojmakinde
Copy link
Contributor

In our application, we have an 'End Date' field for events, and we have multiple checks for the End Date field across multiple parts of the application. The issue is that the 'End Date' field is never used in our application and it usually getting reassigned to the Start Date value, meaning that it lacks much utility as a field. Unless we envisage the possibility of multi-day events, deleting the End Date field from our database might be the path to take.

An instance of assigning End Date to Start Date during event creation:
image

Unnecessary check for End Date in Renew Event (Renew Event also does not have an End Date field in its form):
image

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