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

RFE: Keep Expired Reservations details so that they can be approved after all #531

Closed
vorburger opened this issue Oct 8, 2018 · 3 comments
Labels
Milestone

Comments

@vorburger
Copy link
Contributor

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

I just had a participant pay after their reservation expired (or I was too slow to approve; doesn't matter).

As far as I could see, the only trace one can find in the system in such a case is the E-mail Log? Expired entries do not seem to appear under Reservations anymore - they probably got deleted by the code on expiration.

Describe the solution you'd like
In an ideal world, I guess expired reservation could be kept in the system, shown in an "Expired" tab after Competed / Payment Pending / In Process / Cancelled section in the admin UI, and have a sort of "Resurrect" button.

This would not otherwise change the existing functionality. User would still get the email on expiration exactly like now (that is a great feature).

Describe alternatives you've considered

To work around, one can (and I have) simply Create a new Reservation, manually, copy/paste - not the end of the world either, if it happens just once.

@cbellone cbellone added this to the 2.0 milestone Oct 10, 2018
@cbellone
Copy link
Member

Hi @vorburger,

this is something we can do after 2.0M4 (see #435)

Anyway, right now you can keep reservations whose payment is expired by setting the "Cancel Reservation automatically when payment is overdue" to false (red)

image

@vorburger
Copy link
Contributor Author

right now you can keep reservations whose payment is expired by setting

oh! That's a great tip - thank you.

@cbellone cbellone modified the milestones: 2.0, 2.0-M3 Oct 31, 2019
@cbellone cbellone modified the milestones: 2.0-M3, 2.0-M4 Sep 2, 2020
@stale
Copy link

stale bot commented Sep 3, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Sep 3, 2021
@stale stale bot closed this as completed Sep 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants