Big Issue - Minor User Interface Inefficiencies

One of the big issues of StackSports League Connect scheduling system is the many small inefficiencies in the UI.

For example:
  1. The order of columns in list displays can be rearranged & each resized, but these changes do not persist after you leave that screen.
  2. Filtering lists by various fields is inefficient because it requires use a a single dropdown for all of them, and you then have to type the filters one at a time.
  3. Reloading the browser window does not return you to the screen you were on.

Each of these are issues because:
  1. Many columns are useless or simply not relevant to the task at hand. It is very helpful to move the columns you need to see to the left, and move the others off to the right (you have to scroll to the right to see them, but that's okay because you don't really need to see them anyway). The system does not remember your last layout. And there is no way to save default preferences. So every time you return to that page (which happens all the time, as we are constantly switching back & forth between screens), you either have to resize & rearrange columns again, or just get used scrolling left & right to see everything you need. Very annoying & inefficient.
  2. Filtering lists would be way faster if there was a filter field immediately above each column. There is plenty of screen real estate there and it would save a couple seconds each time. A combo-box with auto-complete would be even better.
  3. Due to the many errors the scheduling system is prone to, we frequently have to reload our web browser (the system tells you do, and other times you come to learn that you simply have to). Refreshing always takes you back to the Divisions & Pools screen. Always. In order to continue your work, you have to then navigate back to the page you were at (usually at least a couple clicks), then rearrange your columns, and also re-add any filter criteria you were using for the list you were working with. It would be amazing if the system would return us to the page we were just on, and even restore the filters we had in place.

I will probably post a video on this later.

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