0
Public bug tracking system
Right now, we submit issues through reports and support tickets. There are some inconveniences :
1. It's hard to properly track a specific bug through forums. There is no proper tag support (ex: severity, category, status like open/closed/reopened, etc.). With the help of bug tracker, it'll be a more organized system allowing easier tracking/searching.
2. Members can't see issues submitted through support tickets. This could cause issue duplication, which cause more resources to be wasted.
We don't necessarily have to pay for services like Jira from atlassian which Mojang uses, as there are also free alternatives. Having a bug tracker allows better issue management, and members also get more detailed information regarding what issues we have, what is fixed, and what is unknown.
1. It's hard to properly track a specific bug through forums. There is no proper tag support (ex: severity, category, status like open/closed/reopened, etc.). With the help of bug tracker, it'll be a more organized system allowing easier tracking/searching.
2. Members can't see issues submitted through support tickets. This could cause issue duplication, which cause more resources to be wasted.
We don't necessarily have to pay for services like Jira from atlassian which Mojang uses, as there are also free alternatives. Having a bug tracker allows better issue management, and members also get more detailed information regarding what issues we have, what is fixed, and what is unknown.
#1206 - Status: closed
6 years ago by LightWayUp for General
Answer: Closed
We would like to keep bugs, glitches and exploits as private as possible tho
Having a public issue tracker would mean sharing with everyone exploits before we could patch them and that would be pretty bad
Tickets for now seem to be good enough for this task, open a ticket, describe the issue, we fix and close
If the issue is already reported there won't be many resources wasted, just few seconds reading the duplicate ticket
Having a public issue tracker would mean sharing with everyone exploits before we could patch them and that would be pretty bad
Tickets for now seem to be good enough for this task, open a ticket, describe the issue, we fix and close
If the issue is already reported there won't be many resources wasted, just few seconds reading the duplicate ticket
6 years ago by NxDs