Team Update 7 Not Properly Accounted for in 4 Alliance Playoff Brackets

[erikorlowski]

Describe the bug
In 4 alliance playoff tournaments, at events with 2 fields, the playoff schedule generated by the scoring system still alternates between field 1 and field 2, not taking into account Team Update 7, which places all matches on field 1.

This has the effect that to properly run a playoff tournament, the Field 1 field display needs to be configured to "All Fields" and referee tablets must also be configured to "All Fields".

To Reproduce
Steps to reproduce the behavior:

1. Generate a tournament with 11-20 teams and 2 fields.
2. Finish qualification matches and alliance selection.
3. Generate the playoff match schedule.
4. View the playoff schedule report and observe that matches are scheduled to alternate between fields 1 and 2, as was the case before Team Update 7.

Expected behavior
All playoff matches will be scheduled for Field 1.

Screenshots
USWISFQ2 - Cycle Time Report.pdf

Device (please complete the following information):

• OS: Windows 11
• Browser: Chrome
• Version: v6.4.1

[pmrobotics]

Interesting, I didn't catch that change in TU07. I'm not sure the table itself makes sense for a single-field playoff -- in our experience hitting 6-minute cycle times on a 1-field event is pretty challenging, especially if there is much in the way of post-event referee discussion as often happens in playoff matches.

4-alliance events are kind of in a grey zone where I could see some tournaments having a single field and other tournaments having two fields. If a 4-alliance tournament is to be played on a single field (and that does make sense for many event), then perhaps the playoff timings should be adjusted for longer cycle times if it's a single-field event?

Pm

[erikorlowski]

I sent an email to FTC team support about the timing issues as well. At our event, the cycles time from match 1 to 2 was 8:36 and 3 to 4 was 8:55 without any unusual delays.

For now, the scoring system generates the expected match times appropriately, but I would like to see those expected start times changed in a team update.

[rachmo]

@erikorlowski thank you for your report. This change was not intended to force running on 1 field, but to show a typical. For events with only 11 teams we got feedback that 1 field was more typical and they were worried this table required them to run an 11 team event with 2 fields, but I see how this change might be unclear the other way.

I apologize for the confusion. We're looking into this, thank you for your patience.