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

Schedule entry move or resize removes additional data #23617

Closed
3 of 4 tasks
terba opened this issue Jan 7, 2025 · 0 comments · Fixed by #23621
Closed
3 of 4 tasks

Schedule entry move or resize removes additional data #23617

terba opened this issue Jan 7, 2025 · 0 comments · Fixed by #23621

Comments

@terba
Copy link

terba commented Jan 7, 2025

Checklist

  • I have updated to the latest available Home Assistant version.
  • I have cleared the cache of my browser.
  • I have tried a different browser to see if it is related to my browser.
  • I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.

Describe the issue you are experiencing

The additional data gets lost when a schedule entry is moved or resized. Tested on Firefox and Chromium on Linux, affects both.

Describe the behavior you expected

When moving or resizing a schedule entry the additional data entered by the user should remain unchanged.

Steps to reproduce the issue

  1. Create an entry in a schedule via the UI (more-info cog icon)
  2. Add an additional attribute to the entry
  3. Move or resize the entry in the calendar view via dragging
  4. The additional data is lost

What version of Home Assistant Core has the issue?

core-2025.1.1

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue?

No response

Which operating system are you using to run this browser?

No response

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

No response

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

Successfully merging a pull request may close this issue.

1 participant