Skip to content

[CAL-2516] Form state changes doesn't lead to change in UI for some fields. #10647

@MehulZR

Description

@MehulZR

Issue Summary

When making some change in the eventType form. The form changes are not reflected in the UI for some fields. They are registerd in the form state but for the UI rendering logic they are dependant on the data fetched from backend.

This can lead to bad UX. The customer can not be sure what is the current form state due to UI mismatch.
The customer may change a field (eg. enabling recurring event), switches the tabs and decides to disables the recurring event. When he switches back to the recurring event tab. He might assume that his changes did not persisted and the recurring event is disabled ( which infact is enabled in the form state ) and leads to unexpected behaivour for the customer.

Steps to Reproduce

  1. Edit a event type(meeting).
  2. Make some changes in a tab and switch between tabs back and forth. ( for eg. lets change the recurring event setting)
  3. The change will be registed in the form state but will not be reflected in the UI.

Actual Results

actual.mp4

Expected Results

expected.mp4

Technical details

  • Browser version: Chrome 115
  • Node.js version: 18.16.1

CAL-2516

Metadata

Metadata

Assignees

Labels

Low priorityCreated by Linear-GitHub SynccommunityCreated by Linear-GitHub Sync🐛 bugSomething isn't working🧹 ImprovementsImprovements to existing features. Mostly UX/UI

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions