Stack Sports Scheduling Errors

I am beginning my second season as a soccer league scheduler using the StackSports League Connect web-based scheduling system. We are required to use this system per our upstream affiliation with NMYSA who elected to move to StackSports due to the requirement from FIFA that all sanctioned/affiliated organizations use a software system that integrates with FIFA's player ID numbers. Apparently the prior system (LeagueOne from Active  Network) didn't meet this requirement.

StackSports has some neat functionality, but also a lot of times many more clicks than LeagueOne to accomplish the same task.

As the scheduler, I have run into many bugs & glitches. I've opened tickets for these, and to my knowledge only one of the 12+ bugs/defects I reported has been fixed.

I believe that fix was a combination of:

  • StackSports had to upgrade the size of server/capacity they were subscribing to in Amazon Web Services.
  • There were some scripts that were created that either resolved some ongoing issues by cleaning them up, or actually optimizing and preventing them.

I was (and still am) grateful for their willingness to spend time to make even the slightest improvements. But there are still many outstanding bugs/defects in their system, which literally seem to have been ignored now for 5 months.

I plan to post here my experiences using this product and hope that by doing so, other StackSports schedulers like myself may also comment and share their experiences, and perhaps together we can help the company focus their development efforts more on fixing the problems in their existing products, rather than deprioritizing this for purchasing and integrating new software into their solution suite to try to sell customers more.

I know when some of our league's leadership has been approached by the StackSports sales reps about purchasing other software products they offer, the response has been that we are not interested in doing this at least until they fix the problems in their product we're already using. Their League Connect product reflects poorly on their company, and is not a good platform from which they can up-sell customers to other products.

Hopefully StackSports will hear their customers, and prioritize fixing the current issues, and then in another 6 months we could be having an entirely different conversation.

Comments

Post a Comment

Popular posts from this blog

StarTech PEXM2SAT3422 initial problems

Image
Background The card: The StarTech PEXM2SAT3422 is a PCIe 4x card featuring 4 SATA ports as: 2 x SATA connector 2 x M.2 NGFF connector It uses the Marvell 88SE9230 chipset The card features RAID 1, 0, 10, as well as SATA pass-through. Upon initially deploying the card, I experienced some very serious problems with it My setup: Server is a SuperMicro X9SCM in a 2U half-depth chassis. 3Ware Card exists with 2 1TB WD Black HDs. Motherboard Intel SATA has 2 Kingston SSDs installed in a RAID1 (Microsoft Dynamic Disk) OS is Server 2012 R2 This server has been rock solid for 3 years. About 1 year ago: I added an Ablecomm SATA card that has 2 M.2 connectors. It has housed a single Crucial CX300 M.2 SATA SSD. This setup has been rock solid with no hiccups whatsoever. Today: I replaced the Ablecomm PCIe card with the StarTech card and moved the CX300. I also installed a 2nd 1TB CX300 alongside. The plan was to mirror the 2 CX300s and start using them for prod...
Read more

Team Conflict Avoidance System Erratic Behavior

The below video shows me discovering conflicting games that were auto-scheduled by the StackSports scheduling system despite a team conflict rule having been previously created to prevent this. Usually the system adheres to the team conflict rules I create. Sometimes (inexplicably) it doesn't. This video is an excellent example showing this is actually a bug, and not intended behavior. After making a subtle adjustment to a game time, it's like the existing team conflict rule "woke up", and triggered the red alerts it should have done all along. In fact it should have scheduled these games in a way to avoid the conflicts in the first place, and therefore the alerts wouldn't have ever had need to exist. This video shows problems such as: Conflicting games that should never have been scheduled at the same time (based on the team conflict rules that were already defined). Missing alert/warnings for "error" games that have problems (i.e. the gam...
Read more

No grace in verbatim communion prayers

Image
I do not appreciate the intolerance for minor grammatical errors in the spoken (typically ‘read’) communion sacrament prayers when recited by the LDS young men during congregation worship services. I understand the covenant nature of the prayer, and thus the importance of the meaning of the covenant being accurately conveyed in the prayer. But the intolerance for minor nuanced accidental variations that do not change the details of the covenant or prayer seems nonsensical. It is disruptive to the service to require the young man to repeat the entire prayer for such an error. And it potentially embarrasses the young man unnecessarily. Considering the degree of grace and leniency church members seem to grant Joseph Smith for much more significant variations in details he communicated (such as stating he was 14 years old, and also that he was 16 years old, when he had his first vision), I don’t understand why we can’t grant our young men a bit of grace for a much-less significant nuanced...
Read more