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

[Feature request]: Optional Auto-Archive for Completed Bookings #1679

Open
carlosvirreira opened this issue Mar 13, 2025 · 0 comments
Open

Comments

@carlosvirreira
Copy link
Contributor

Contact Details

No response

Is your feature request related to a problem? Please describe?

Currently, when a booking is complete, it remains visible in the booking list. This requires users to scroll past completed bookings to find the active ones they're looking for, creating unnecessary friction in the workflow. However, some users may want to keep completed bookings visible for various reasons.


Implement an optional automatic archiving function for bookings that have been completed for a user-defined period (default suggestion: 48 hours). This would give users control over whether and when completed bookings are removed from the main booking list view.

Describe the solution you'd like

Add a configurable auto-archive feature that would:

  • Include a user preference setting to enable/disable the auto-archive functionality
  • Allow users to set their preferred time period before archiving (24 hours, 48 hours, 1 week, etc.)
  • Automatically move bookings to an archive section after the selected time period when enabled
  • Provide easy access to archived bookings through a separate view or filter
  • Include a visual indicator showing that auto-archive is enabled/disabled

Benefits

  • Gives users choice and control over their booking list
  • Accommodates different workflow preferences
  • Still maintains the "low complexity score" while adding user flexibility
  • Respects that different users and organizations have different needs

Describe alternatives you've considered

No response

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant