RetroAchievements / RetroAchievements/RABot
[Feature]: QA report forwarding command
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Problem or Use Case
QA often gets reports of missable tags or minor issues that are not appropriate for a ticket for content that has an active developer. The current process is to manually go to the QA message box, type a message similar to:
"Hello [dev], we received the following report and wanted to pass it along for your consideration/action. No follow up with QA is necessary unless you have questions. Thanks for your assistance.
-QA"
Proposed Solution
Add a /transfer command when used in a thread created by RABot in response to a received message, sends a message to the active developer that includes the above standard upfront message + the full player report.
"/transfer Ghal416" would the following message to RA user Ghal416 if used in https://discord.com/channels/476211979464343552/1420897361781198878
Hello Ghal416, we received the following report and wanted to pass it along for your consideration/action. No follow up with QA is necessary unless you have questions. Thanks for your assistance.
-QA
======================
Report:
https://retroachievements.org/achievement/276914
I'd like to report a misclassification error in Intermediate Denizen (5):
Missable if the silver medal is previously obtained.
Really, the only challenge behind this achievement is noticing it's actually missable in the first place. Nothing in the intermediate course demands or is made easier by the animal friends you can have at this point.
The entire set is a hodgepodge case of unmarked missables. Damageless bosses you can't refight, dungeon sections that can't be redone, etc.
Alternative Solutions
No response
Command Type Preference
Slash command (/) - Preferred
Feature Scope
All users
Usage Examples
No response
Additional Context
No response
Checklist
- I have searched existing issues to ensure this feature hasn't been requested
- This feature would be useful to multiple users, not just me
- I have provided clear use cases and examples
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Discord command handlers and the code that creates RABot response threads. Trace how received reports and active developers are identified, then define the /transfer command's thread and recipient behavior. Done means the standard QA message and full report are forwarded to the named developer when invoked in an eligible thread.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100