04

WB Games Bugs

We needed a way for gamers to be able to tell WB Games what bugs were important to them and the game developers needed enough information to be able to address the issue. So how do you make a platform that’s easy enough for the average gamer, but configurable and detailed enough for professional qa analysts? Oh! And it has to be able to integrate with Jira.

WB Games required an application that was cost-effective and could scale easily for use with multiple games. To accomplish this, we opted to employ serverless technologies and a multi-tenant architecture. Additionally, micro-interactions were implemented to enhance user experience and minimize friction.

During onboarding, users are prompted to add their platform specs that will auto-populate fields during bug reporting. Bug drafts are then saved in local storage after every keystroke to prevent users from losing their work.

For bug discovery, elastic search is used to help users find the most relevant bug to their query. Users are able to vote on bugs to tell developers which issues are most important to them. They are able to see which of the community’s bugs are currently being fixed, which ones have been resolved, and which ones have been marked as closed. Users can also help validate that bugs are reproducible and flag any issues to WB Games staff.

For WB Games staff, bugs are able to be automatically exported to their development team’s internal Jira. Once exported, the ticket is automatically monitored and WB Games staff are kept informed — adjusting the ticket status for the public.