ilaripih/lts-booking

Court booking system for Lappeenrannan Tennisseura Ry

lts-booking's Issues

Admin can add compulsory user details

Admin users should be able to set required user details for normal users before they can make bookings. The following types should be supported:

• Text
• Dropdown (single selection is enough)
• Optional dependency on another option + value pair
• Make the custom details user-configurable
• Handle custom user details on server-side
• Show custom user details on /user page
• Prevent bookings with incomplete custom user details

Time estimate: 4h

Limit active bookings to n at a time

Admin users should be able to set a court-specific limit for the number of active bookings per customer.

Time estimate: 2h

Booking cancellation period should be configurable

Currently cancellations need to be made 8 hours before the booking. But it should be configurable by admin (a global setting is fine).

Time estimate: 2h

Email confirmation and verification

When creating a new user account, an activation link should be sent to the user's email.

Time estimate: 4h

Admin can lock/unlock users from logging in

Time estimate: 1h

Show past bookings

Currently past time slots are greyed out but it would be useful to show bookings for the past.

Time estimate: 1h

Option to hide inactive users

On the Users page admin should be able to toggle the visibility of deactivated users. This should also affect the CSV export.

mark a custom field as unique

Admin should be able to define a custom user field as unique.

Time estimate: 1.5h

Weekly recurring bookings

Admin users should be able to make bookings that repeat every week. This is clearer than just keeping the court closed at those times.

Time estimate: 4h

Excel/CSV export for user data

Admin users should be able to export Excel/CSV from the /users page

trim whitespace from username when registering account

Time estimate: 0.5h

Allow splitting courts into groups

For example, we could have groups Tennis, Badminton and Gym. Then the UI would be less cluttered.

• Configurable groups
• Group is configurable in courts
• Group filter for calendar page

Time estimate: 4h

duplicate bookings in UI

In lylyvaraukset.com it's possible to make duplicate bookings by pressing the "Save" button repeatedly. Doesn't reproduce in dev env.

Admin should be able to create new users

It should be possible for an admin to close the system so that new users can only be created by an admin. Alternatively an admin should approve or reject new user registrations.

Time estimate: 6h

Limit bookings to n hours

Admin users should be able to set a court-specific maximum length for bookings.

Time estimate: 2h

column sorting in users list

It should be possible to sort the users list with any column.

Time estimate: 1h

Admin should be able to reset a user's password

The Users list should show a "Reset password" button for each user. After resetting the password, it should be shown to the admin user.

list unpaid bookings

We need a separate listing for unpaid bookings. Features needed:

• filter by booking user or booking title (in case admin made the booking and set customer's name as title)
• show number of items in the list
• sort by booking date

As recurring bookings are currently only supported for admins, they can be always filtered out. But normal bookings, even when created by admins, should be shown.

The booking system name should be configurable

This is no longer just for Lappeenrannan tennisseura (LTS).

Time estimate: 1h

Admin should be able to delete users

Include a trash can button next to users.

ignore opening hours if the court opens and closes at the same time

disable self-linking courts

Currently it's possible to link a court to itself. It should be prevented.

hour precision in booking

It should be possible to set a court-specific settings that controls whether bookings for the court use half-hour or hour precision. It's enough to enforce this client-side.

book a group of courts

The system needs a "view" type court that is actually a pointer to multiple other courts.

• In court editor, have a multi-select dropdown for selecting the actual courts; otherwise the court is a real court
• Make actual bookings to the real courts when booking the group
• In "My Bookings" list, filter out bookings to the real courts if the booking was made to group
• When a group booking is cancelled/removed, remove the bookings to the real courts
• In calendar view, don't create "book" link to time slots where one of the linked courts is unavailable
• In booking view, don't allow invalid duration