bug: Calendar event color changes not saved/persisted when editing #109

New Issue

2026-05-11T15:03:32Z

enjin2310 commented

2026-05-11 15:03:32 +00:00

When editing a calendar event and changing its color, the color changes are not properly saved or persisted.

Observed behavior:

User opens an event details dialog and selects a new color from the Event Color palette.
The color change appears in the preview of the event.
After saving the changes, the event reverts to its default color instead of retaining the selected color.
The attached screenshots show the Event Details dialog with color selection and the preview displaying the new color, but the changes fail to persist.

Expected behavior:

When a user selects a new event color and saves the event, that color should be saved to the event.
The event should display the newly selected color on the calendar after saving.
Color changes should persist across page reloads and future edits.

Steps to reproduce:

Click on an event to open Event Details.
Select a different color from the Event Color palette.
Observe the preview updates with the new color.
Click Save Changes.
Verify the event color on the calendar.
Result: Event reverts to default color instead of showing the selected color.

Classification:

Type: bug
Area: Calendar / event editing / color persistence
Severity: medium
Impact: Users cannot customize event colors; changes are lost after saving

When editing a calendar event and changing its color, the color changes are not properly saved or persisted. Observed behavior: - User opens an event details dialog and selects a new color from the Event Color palette. - The color change appears in the preview of the event. - After saving the changes, the event reverts to its default color instead of retaining the selected color. - The attached screenshots show the Event Details dialog with color selection and the preview displaying the new color, but the changes fail to persist. Expected behavior: - When a user selects a new event color and saves the event, that color should be saved to the event. - The event should display the newly selected color on the calendar after saving. - Color changes should persist across page reloads and future edits. Steps to reproduce: 1. Click on an event to open Event Details. 2. Select a different color from the Event Color palette. 3. Observe the preview updates with the new color. 4. Click Save Changes. 5. Verify the event color on the calendar. 6. Result: Event reverts to default color instead of showing the selected color. Classification: - Type: bug - Area: Calendar / event editing / color persistence - Severity: medium - Impact: Users cannot customize event colors; changes are lost after saving

Screenshot 2026-05-11 110158.png

179 KiB

Screenshot 2026-05-11 110210.png

139 KiB

spikerj commented

2026-06-10 00:06:03 +00:00

Fixed in spikersoft-angular PR #35 (merged to master). Drag/resize updates now carry the full event payload so color/description/location survive the backend's full-replace PUT. Closing.

spikerj closed this issue

2026-06-10 00:06:25 +00:00

spikerj referenced this issue

2026-07-03 22:46:22 +00:00

[Bug] /api/system/version rate limiter rejects with 503 instead of 429 (RejectionStatusCode default) #341

spikerj referenced this issue

2026-07-03 23:13:14 +00:00

[Bug] /api/system/version rate limiter rejects with 503 instead of 429 (RejectionStatusCode default) #341

spikerj referenced this issue

2026-07-06 02:37:45 +00:00

art_pipe observability #1 (.NET): propagate W3C traceparent into the worker + per-stage child span #429

spikerj referenced this issue