Bug tracker

A significant number of issues in the bug tracker are already fixed in a release version, duplicates remaining open, reported in error, or have descriptions that are so vague as to essentially be useless. There are over 10000 open issues for MCPE (vs 6100 for JE).

Observed Behavior

1. Tickets are left unresolved after the version containing the fix is released. Examples: MCPE-45935, MCPE-47324.

2. Duplicate tickets are left open for a long time after they are reliably reported as being a duplicate. Example: MCPE-58877 reported by a "Helper" as a duplicate on 13/Dec/19 but not resolved as such until 24/Jan/20.

3. Tickets that are reported as fixed or erroneously submitted are left open. Examples: MCPE-62364 (hardware error), MCPE-44254 (reported in one beta, did not occur in next beta or since).

4. Many tickets have descriptions that are too vague to be useful in searching. Examples: numerous, MCPE-62357, MCPE-62356

5. Tickets never get a status of "In Progress", though there are reliable reports in comments they are actively being worked on. Example: MCPE-57330. Notably, the MC-... bugs (Java Edition) do have tickets set to In Progress.

Expected Behavior

1. Once the version is released the system will either automatically resolve the ticket or there will be a systematic effort to do so.

2. When a ticket is reported to be a duplicate it will get resolved within a few days as such.

3. The submitter would have the ability to retract or resolve the ticket.

4. Descriptions would be edited by knowledgeable persons to make them clear and useful for searching.

5. Tickets would get a status: In Progress when the developers are working on a solution. Notably

A systematic effort to "clean up" the bug tracker for MCPE would aid the developers in finding out about the important bugs, as well as the community in avoiding duplicate reporting. Furthermore, apparently the reporter has to "watch" their own bug reports to get notifications for them, where this should be automatic.