Create ticketing system for tab corrections

[tienne-B]

This would be a very big project, but could make tending to participant requests much easier without needing an external Google Form or inbox. Having a system for participants to correct information within the Tabbycat system would allow for the tab team to have a way to automatically perform the requested change based on the request.

There are a few types of request to envision:

• Adding conflicts This might be better left off for now to be handled by the tournament's equity team before input, and to avoid Tabbycat being used to handle complaints.
• Correcting participant information (including speaker/break categories)
• Signaling problematic results

On the participant's side, there could be a "Report a problem" button on their private URL which proposes the options of types of request, which then leads to a form to ask more details:

• For conflicts, a list of participants/institutions to select 1 from;
• For participant information, which field to correct and the requested value;
• For problematic results, which round should be verified.

All of them would also have a text box for their motive. The form would have to be capable with the polymorphic types as speaker categories would be a <select but name would be a short text input.

On the tab side, new requests are shown when submitted with a new websocket, and could replace the "Latest Results" on the tournament overview. Then, a user can open the ticket, and accept (which will make the requested change) or reject. Assigning members would be out-of-scope.

When resolved, the user may be notified with an email, or shown on their private URL page.

Thoughts?

[dictumhindi]

I am trying to deploy to render and every time it says detected node 16.15.1 and deployment fails. I don’t know anything about coding. Need for a tournament

[linh-trant]

It would be nice if this system could be located under "Submit feedback". It would be a plus if it shares the same format/style/layout with "Submit feedback" too, making it easier to be used.

I would suggest another type of request: report equity violation. I know equity-related problems should be addressed directly to the Equity team, but I have known too many equity violation cases which were kept in the dark because people were too scared to speak out. It would be great if the participants can choose if they want to submit their problem anonymously or not.

[czlee]

Seems like it might be nice. Would it be easier / more featured to integrate with an existing ticketing system? (My guess is they'd be about the same, as the level of integration we'd want to make this really effective would probably pose quite a barrier.)

[Veyron2121]

I would caution against reporting equity violations directly on TabbyCat, and instead allow for a button that links to an Equity form that only the Equity team could see!

[philipbelesky]

Agree with the above, I think that Equity teams should always have autonomous control over that process, and I would expect that a good equity team should accomodate anonymity if desired. Even with Tabbycat's user permissions system there are always some superusers or people with database access; both provide vectors for accessing sensitive data. Even cases of unintentional access present a new harm to tab staff alongside the obvious harms posed to participants in the equity process.