Skip to content

[CAL-5375] Clearly mark rescheduled bookings in UI #20398

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

Closed
CarinaWolli opened this issue Mar 27, 2025 · 1 comment · Fixed by #20401
Closed

[CAL-5375] Clearly mark rescheduled bookings in UI #20398

CarinaWolli opened this issue Mar 27, 2025 · 1 comment · Fixed by #20401
Labels
bookings area: bookings, availability, timezones, double booking consumer 🧹 Improvements Improvements to existing features. Mostly UX/UI Medium priority Created by Linear-GitHub Sync ui area: UI, frontend, button, form, input

Comments

@CarinaWolli
Copy link
Member

  • Add a rescheduled badge in the booking list with a tooltip 'Rescheduled by …'
  • On the bookings details page (/booking/uid) add 'Rescheduled by …' under reschedule reason with a link to the original booking

From SyncLinear.com | CAL-5375

@CarinaWolli CarinaWolli added consumer Medium priority Created by Linear-GitHub Sync labels Mar 27, 2025
@dosubot dosubot bot added bookings area: bookings, availability, timezones, double booking ui area: UI, frontend, button, form, input 🧹 Improvements Improvements to existing features. Mostly UX/UI labels Mar 27, 2025
@sankalpaacharya
Copy link

I'd like to work on this feature. I understand it involves adding a rescheduled badge to the booking list with tooltips and additional information on the booking details page. Is this still available to be worked on?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bookings area: bookings, availability, timezones, double booking consumer 🧹 Improvements Improvements to existing features. Mostly UX/UI Medium priority Created by Linear-GitHub Sync ui area: UI, frontend, button, form, input
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants