Hey folks,
The Bug Submission Form has provided our team with more informative reports, allowing them to reproduce, file, and resolve issues more efficiently. We understand that it lacks collaborative and tracking elements for a wider audience, but it has solved other challenges we’ve experienced with tracking bugs on AnswerHub internally. If you’d like to see what input your fellow devs may have, then feel free to share your to AnswerHub as well.
In recent weeks, the form was shifted to a new backend. This doesn’t affect what you see, but it did simplify the process for the team, allowing them to more effectively communicate with submitters.
Most tickets receive a response, often resulting with either:
- A direct link to the new on the public tracker,
- A request for repro steps,
- Notification of the bug being a duplicate, or
- Notification of the “working as intended."
In the event of the latter, always feel free to post this to the Feedback for Epic thread. We, the community team, compile requests from here and pass them along to our dev teams. Down the line, we hope to build a more robust tool for reporting these requests.
Submissions that are unrelated to engine development, such as reports concerning Fortnite or spam, will immediately be closed with no notification.
Please understand that the Bug Submission Form has never been intended to be the “new AnswerHub.” It’s been implemented to help us push higher quality bugs through to our dev teams, while we work on a better, long-term solution.