Outside teams can't view print a concise schedule and their contact info is inaccessible

This is one of the more frustrating issues because it affects more than just me. Our league has 18 outside teams this season who are not member-affiliates of our league and don't use StackSports. As a result, we enter these teams manually using the "Outside Teams" functionality of the League Connect system.

Unfortunately there is a bug that prevents these teams from viewing or printing their concise schedule, and also prevents the coaches contact info from being accessible. This means coaches can't easily get the team's contact info when they need to coordinate details (such as for reschedules due to rain outs, etc.). I often receive these contact requests during the season and slow the process down for everyone. Although we can (and do) distribute a coach contact list, this bug is still a pain because people become accustomed to the convenient functionality.

Also, for teams to not be able to filter the schedule down to their own games is a pain for them. There's no work-around for that one, other than forcing them (or me) to use an inefficient manual process.

This has been one of my big bugs I reported many months ago and followed up on, and was eventually told by tech support, that after conferring with their product managers (or developers), this is in fact the behavior by design? What! That is ridiculous and impossible to believe. The people who developed League Connect (Bonzi) were very smart software developers. Despite its bugs and inefficiencies, it is a thoughtfully designed sophisticated web application. There is no way they would have intentionally designed it to display the message "Schedule and games are no longer available for this event." when you try to filter the view to the games for an outside team. That error isn't even accurate in the first place.




In the example in this video, 2 teams were outside teams, and three are internal teams from affiliate member clubs.


Here is the email in which their tech support lead told me this functionality is by design:
I have blocked out his name & contact info, as I don't think he holds any responsibility for these issues. He's just the messenger.

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