BUGS 2
Final Furlong Bugs
Bugs, feature requests, and other tracking for Final Furlong
Quick search  
Previous open issue Go to previous open issue Previous issue Go to previous issue   Go to next issue Next issue Go to next open issue Next open issue
#22  -  Add options to future entries Posted Jun 27, 02:23
Last updated Jun 27, 02:26
Product Final Furlong
Edition(s) 4.0
 
Issue type Enhancements
Posted by
Shanthi
Owned by
Not owned by anyone
Assigned to
Not assigned to anyone
Status
 
Not reviewed
Category General category
Resolution
Not determined
Reproducability
Not determined
Severity Low
Priority
Not determined
Estimated time
Not determined
Elapsed time
Not determined
Progress
   
Targetted for
This issue has no target milestone
Votes for this issue
1 votes for reviewing
0 votes for critical status
0 votes for closing this issue
Add a vote for
Items attached to this issue
There are no items attached to this issue
Issue(s) which this issue depends on to be solved
Issue(s) which depends on this issue to be solved
Reports
Affected by this issue Status Confirmed
Current (06/26/09) (4.0.0)
 
Not determined
Entering Races
 
Not determined
Description and details
From Cricket Hill:

Shanthi, I know you\'ve got a lot on your plate, but I figured I would throw this out there. I know it\'ll be awhile before future entries goes live due to all the variables tied up with that. So, I was wondering if it might be possible to tie future entries to a stable alert that would let us know a week ahead of a race that we had \"entered\" our horse, Billy Bob Sue, into race #12 on 2/4/2013. As owner, I could be like, \"Oh, I have to enter Billy Bob Sue into race #12 on 2/4/2013. Entries have just opened, so I\'ll go do that right now!\"

For me, personally, that would be way more helpful than having pre-entries work the way you\'re planning. I\'m horrible at remember what I\'ve done in the past, and if I did pre-enter my horse in race #12 on 2/4/2013 way back on 1/4/2013, there\'s a darn good chance that I will have forgotten I had entered him there and race him on 1/31 at a different track. If pre-entries worked 100%, my tuckered out horse would then be shipped to another track ($ I didn\'t want to spend) to run in race #12 on 2/4/2013 and break his leg because I can\'t remember anything and your code is awesome beyond words.

However, if I had a stable alert that told me I had planned to race him in race #12 on 2/4/2013, I could decide, well, I don\'t think I want him to run that race, and just ignore/dismiss the alert in general.

I hope this somehow makes sense. I also hope this\'ll be a snap for you to implement if you think it\'s worth your time.
How to reproduce
N/A
Tasks  (click to view details) Assigned to Last updated Status Completed
No tasks are specified for this issue