Skip to content

misode/mojira.dev

Repository files navigation

A mirror of the Minecraft bug tracker written in Go

Homepage of mojira.dev

Why do we need this?

Since the migration the public bug tracker has been very slow and unfriendly to work with. There are two official platforms: bugs.mojang.com and report.bugs.mojang.com. Both platforms expose part of an issue's metadata, but getting the full picture is difficult.

How does this work?

The Go server uses the public, servicedesk, and legacy APIs to mirror issues. There are currently 3 systems in place to make sure issues are as much in-sync as possible:

  1. A full sweep sync of issues runs in the background. With currently around 590000 issue keys, this process can take around 4 days.
  2. The server actively polls a list of recently updated issues every few seconds and adds them to a queue, which is later processed.
  3. Whenever an issue is requested in the frontend and it hasn't been synced within the last 5 minutes, it refreshes the issue.
Issue detail page

About

Work in progress mirror of the Minecraft bug tracker

Resources

Stars

Watchers

Forks

Sponsor this project

  •