Tanvir Ahmed Arnab Gameplay Systems

Software project / internal tooling

Game Bug Tracker

Game Bug Tracker is a .NET 10 Razor Pages app I am building to organize bug reports for a single game project. The current phase is about getting the tracker foundation right before expanding into a fuller reporting and update workflow.

ASP.NET Core Razor Pages .NET 10 Internal tooling

Current state: app shell, bug-report model, project scope, and V1 workflow targets are in place. CRUD pages and persistence are the next milestone.

Role Solo developer
Stack ASP.NET Core Razor Pages, C#, .NET 10, Bootstrap
Focus Internal game-project bug triage
Status Active work in progress

Project goal

The goal for version 1 is to create a simple internal tracker for one game project. Instead of starting with a broad public-facing system, I am focusing first on the workflow a developer actually needs during active production: logging issues, keeping status readable, and building a clear backlog of what needs attention next.

What is implemented right now

  • An ASP.NET Core Razor Pages application targeting .NET 10 with HTTPS-ready startup configuration.
  • A shared layout and navigation structure that establishes the shell for the tracker interface.
  • A BugReport model with title, description, severity, status, and created timestamp fields.
  • Enum types for BugSeverity and BugStatus to keep report state consistent.
  • A project homepage that defines the version 1 scope and clarifies the first workflow goals.

Version 1 roadmap

  • List bug reports in a clean internal dashboard.
  • Create new bug reports without needing to edit code directly.
  • Open a detail view for individual reports.
  • Update bug status and severity as issues move through triage.

Why this project matters to the portfolio

This project connects two things I care about: game development and practical software workflows. It is not just about storing bug data. It is about designing a tool that helps a real project stay organized, keeps priorities visible, and supports the less glamorous but very important side of actually shipping and maintaining work.

What comes next

The next major step is moving from scope and model design into the actual CRUD flow: pages for listing, creating, viewing, and updating reports. After that, I want to improve persistence, filtering, and eventually explore how player-submitted bug reports could fit into a later version without overcomplicating the early build.