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

Enhancement: Schedulable entry per brewer increases #1547

Closed
JLowe-N opened this issue Jul 6, 2024 · 8 comments
Closed

Enhancement: Schedulable entry per brewer increases #1547

JLowe-N opened this issue Jul 6, 2024 · 8 comments
Assignees
Labels
enhancement Suggestion for future enhancement. in latest master commit Fix is in latest commit to master. Not in release. v2.7.1

Comments

@JLowe-N
Copy link

JLowe-N commented Jul 6, 2024

Competitions fill up fast these days, often within the first hour. The only lever we have to pull is constraining the total entries per brewer or per style. To allow more Brewers the opportunity to enter a competition, it would be useful to have a rolling entry limit per user following a schedule.

Day 1: 4 entries per brewer
Day 2: 8 entries per brewer
Day 3: 12 entries per brewer
Day 4: 24 entries per brewer

The best schedule may differ per competition, but the ability to increase the entry limit per brewer over time would be useful.

This ensures competitions can both hit their target entries, while also giving more Brewers a chance to compete.

@JLowe-N JLowe-N added the enhancement Suggestion for future enhancement. label Jul 6, 2024
@ercousin
Copy link

ercousin commented Jul 6, 2024

+1 to this, I would also use this

@geoffhumphrey geoffhumphrey self-assigned this Aug 7, 2024
@geoffhumphrey geoffhumphrey added this to the v2.7.1 Release milestone Aug 7, 2024
@geoffhumphrey
Copy link
Owner

Hi @JLowe-N - thanks for the suggestion. I too have seen the "storm the gates" phenomenon compound in recent months and agree that this would be a great way of letting the system take care of something that is a manual process now. For the next version, 2.7.1, this will be the only enhancement that will be included in the package.

The way it will work is that Admins, via Admin Dashboard > Preferences > Site Preferences, will be able to specify up to four tiers of per participant entry limits, each bound to a number of days from the entry open date.

Like so:

image

Participants can review all scheduled entry limits by going to the Info page. Under the Per Entrant Limits heading, there will be a table:

image

Note that the current limit is highlighted in blue. If there is an overall per-entry limit, it will be in the final row in the table along with the entry close date.

Participants will also be advised of the current limit in the account summary sidebar section of their My Account page:

image

The goal is to release 2.7.1 by the middle of August, 2024.

@JLowe-N
Copy link
Author

JLowe-N commented Aug 7, 2024

Thanks for accepting and building this feature! This looks just like I imagined and better with the clear communication on limit steps.

@jimmyorkin
Copy link

I want a slightly derogatory handle for the folks that "Storm the Gates". "Stormers" or "Gaters"?

@JLowe-N
Copy link
Author

JLowe-N commented Aug 7, 2024 via email

@geoffhumphrey geoffhumphrey added the in latest master commit Fix is in latest commit to master. Not in release. label Aug 11, 2024
@hirendu
Copy link

hirendu commented Aug 23, 2024

This is an awesome feature. Could we get this feature on the hosted comp (chc.brewingcompetitions.com)?

@geoffhumphrey
Copy link
Owner

It will be incorporated into version 2.7.1. Once that has been tested and I'm confident it's ready for release, all hosted sites will be updated.

@geoffhumphrey
Copy link
Owner

@hirendu - please note that 2.7.1 was released earlier today - all hosted installations have been updated. You can now utilize this feature for the CHC!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Suggestion for future enhancement. in latest master commit Fix is in latest commit to master. Not in release. v2.7.1
Projects
None yet
Development

No branches or pull requests

5 participants