Skip to content

Past call bookings shouldn’t have the cancel event option. #22370

@mursaleen-nisar

Description

@mursaleen-nisar

Proposal

Currently, users are able to see and use the "Cancel Event" option even for past call bookings. This behavior is misleading, as canceling an event that has already occurred has no practical effect and may lead to confusion or misuse.

Suggested Solution

  • Disable or hide the "Cancel Event" button for any call bookings that are in the past (i.e., where the event end time is earlier than the current time).
  • Ensure the UI reflects this change consistently across all relevant views (e.g., booking details page, event list, etc.).
  • Optionally, provide a tooltip or status indicator to explain that past events cannot be cancelled.

Benefits

  • Improves user experience by preventing actions that are no longer valid.
  • Reduces potential for errors or misunderstandings around event management.
  • Maintains a clearer distinction between past and upcoming bookings in terms of available actions.

Notes

If cancellation of past events is currently being logged or triggering backend workflows, ensure this logic is updated accordingly to prevent unnecessary processing.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Medium priorityCreated by Linear-GitHub SynccommunityCreated by Linear-GitHub SyncconsumerlinearSync Github Issue from community members to Linear.app✨ featureNew feature or request🧹 ImprovementsImprovements to existing features. Mostly UX/UI

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions