Calendar event pages showed hardcoded times (e.g. 11:00 AM - 3:00 PM) because CalendarEvent only stored dates (start_date / end_date). Admins had no way to set a real time range.
Goal
Add optional start_time and end_time fields on CalendarEvent
Expose them in Django admin
Render times from the model on calendar templates (hide when unset)
Cover formatting with unit tests
Acceptance criteria
Admin can set start/end times when creating/editing an event
Calendar UI shows the configured time range
Events without times omit the Time row
Migration applied; tests pass
## Problem
Calendar event pages showed hardcoded times (e.g. `11:00 AM - 3:00 PM`) because `CalendarEvent` only stored dates (`start_date` / `end_date`). Admins had no way to set a real time range.
## Goal
- Add optional `start_time` and `end_time` fields on `CalendarEvent`
- Expose them in Django admin
- Render times from the model on calendar templates (hide when unset)
- Cover formatting with unit tests
## Acceptance criteria
- [ ] Admin can set start/end times when creating/editing an event
- [ ] Calendar UI shows the configured time range
- [ ] Events without times omit the Time row
- [ ] Migration applied; tests pass
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
Calendar event pages showed hardcoded times (e.g.
11:00 AM - 3:00 PM) becauseCalendarEventonly stored dates (start_date/end_date). Admins had no way to set a real time range.Goal
start_timeandend_timefields onCalendarEventAcceptance criteria