FIRST-Tech-Challenge / FIRST-Tech-Challenge/scorekeeper

FTC-Events shows old "Robot Name" identifier

Open
#819 0 comments 0 reactions 0 assignees View on GitHub
bug ftc-events
Dominant language
No language data
Stars
110
Forks
26
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
FTC-Events shows "Robot Name" from a previous season in current season team information, despite the field which populates that "Robot Name" data no longer being accessible to teams. This data is outdated by several seasons, but because the "Year" value displays the current season year, someone who doesn't know this information is deprecated might think it's current.

**To Reproduce**
Steps to reproduce the behavior:
1. Go to FTC-Events
2. Go to a Team Number that had a Robot Name populated in TIMS before the TARDIS implementation]
3. See error

**Expected behavior**
Remove this deprecated and outdated information from view on the frontend. The data isn't doing any harm in the db on the backend, but it just shouldn't be displayed on the frontend since it's outdated.

**Screenshots**
Screenshot 2024-12-29 at 12 31 10 AM

**Device (please complete the following information):**
- OS: macOS 15.2 Sequoia
- Browser: Chrome
- Version: 131

**Additional context**
The old "Robot Name" field, which used to be fillable by teams back when TIMS was still a thing, is no longer accessible to teams and hasn't been since TARDIS was implemented. However, it seems that since the 2020-2021 season, the last Robot Name that was entered into TIMS prior to the TARDIS implementation has been shown on FTC-Events for each subsequent season, despite the teams no longer being able to change it or remove it from their profile.

I had a conversation with Danny Diaz about this back in November, and he told me that the issue is that FTC-Events is just displaying old information from a deprecated field in the database on the backend, and it just hasn't been a priority to remove it from view in the frontend on FTC-Events. Totally understandable - just want to submit this on GitHub for the sake of following the "established procedure".

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.