Bug Reporting Tool for UE 5
One of the recurring challenges I encountered in multiple team projects was the inefficient bug reporting and fixing workflow. To address this, I developed a custom plugin in Unreal Engine 5 that integrates seamlessly with Codecks.
Originally built to work with Jira, the tool was later adapted for Codecks to align with our scrum processes. By enabling developers to submit and track bugs directly within the UE5 editor, the plugin helps ensure that all team members stay up to date on current issues.
The tool is also published on Fab for Unreal Engine 5.4/5.5 and can be found here.
The repository for this project can be found here.
-
Role: Tools Programmer
-
Features:
-
Dedicated Unreal Engine 5 plugin for bug reporting with Codecks.
-
Integration with Codecks’ API
-
-
Project Information:
-
Team size: Started as part of a team project, finished as a solo project
-
Duration: 1 month
-
-
Tools/Language:
-
Unreal Engine 5
-
C++
-
Reporting a bug
-
The tool allows users to create bug reports directly from within the engine or at runtime and sending them to Codecks.
-
To reduce the effort of manual reporting, developers can generate structured tasks directly from the engine, ensuring that no issue goes unnoticed.
-
Since some issues are better explained visually, users can also attach a screenshot of the current game view or include relevant local files along with their report.
In-engine bug list
-
Beyond just reporting, the tool also fetches existing bug reports from Codecks and displays them within the engine.
-
This makes it easy for developers to track ongoing issues and work directly from the engine without needing to switch between multiple tools.
Team Impact
-
Once the team became familiar with the tool, they started reporting bugs more consistently and found it to be a valuable addition because they had a similar experience in previous projects, where bugs often went unreported for long periods, causing unnecessary delays.
-
With this system in place, we were able to spend more time fixing issues rather than tracking them down, ultimately leading to a smoother development process and a higher-quality game.
Accessibility
People are more likely to use a tool if it's easy to use and responsive, so I added some features that I thought would improve that:
-
The ability to select the deck in which the bug goes and also a default deck - only in editor
-
Messages for the success or failure of an action like saving the organization name
-
Multiple file selection for uploading local files, and also easy removal from the list
