Go ahead and resolve this as invalid, I just need some answers and I didn’t know where else to post these questions.
Why are some reports closed or hidden (when they are not a security issue)?
How important is to confirm that a bug exists in outdated versions?
Is there a way to “mark” a bug so you can find it in the future (other than watching it)?
Is it possible to change your username on the bug tracker?
How is the main post determined for duplicates? It’s usually the oldest one, but not always.
What’s the difference between “Invalid” and “Works as Intended”? I’ve seen them used pretty much interchangeably.
What is the “Done” resolution for? It doesn’t seem to actually be used.
What are the requirements and responsibilities of being a mod?
Is there any way to see who uploaded a screenshot?
What does the grey line between some listed duplicates mean?
Why do mods sometimes suggest that a player makes a new bug report? Wouldn’t be better to just update the current report?
Why do some bugs duplicate other duplicates? Shouldn’t they all link to the main report?
In what order are issues displayed in a search? Is there a way to specify a preferred order?
How do mods decide if an issue is intended? Is it just their opinion?
Is there a way for the reporter to remove a screenshot from their report?
There seems to be a bug that is causing me to not get some of the notification emails when a report I’m watching is changed. Does anyone know how to fix this?
Where does one report bugs that affect the bug tracker?
Where should I ask questions like this in the future?
Comments 19
How do I change it?
Just to add to some of the info:
1. Though the privacy settings are used for hiding security issues and such, reports may be trashed completely (not publicly visible), if the report is essentially useless and contains no information.
2. If a bug only exists for an outdated version, it is typically considered fixed for a current or future version
6. Moderators will typically resolve as invalid, even when it could be Works as Intended, because the latter is considered an official resolution by Mojang. We do however occasionally resolve it as such ourselves, on the more obvious reports.
16. If information is added/changed via the Update Issue button, it will not send a notification email.
17. Note that, although issues can be reported and fixed about the JIRA platform, the version hosted by Mojang is not automatically updated and synchronized, and will (probably eventually) be updated to fix certain issues. The previous attempt to update resulted in unexpected behaviour, and was thus reverted.
1. Some of the "hidden" tickets you might stumble upon are ones that have been trashed – they're spam, accidentally created tickets, exact copies of existing tickets, that sort of thing.
6. Invalid means that the ticket shouldn't have been created in the first place. It's a question, a feature request, tech support, a misunderstanding, etc. Works As Intended is for when it is conceptually possible that the behavior described might be a bug, but we have confirmation that it's intended behavior, whether it be from a public statement from Mojang, or just asking them ourselves.
8. Requirements? Only a Mojangsta could really say, since they're the ones who picked us. But basically, our job is to manage the bug tracker for them, to filter out all the noise so that they can get a concise list of current bugs. That means testing issues, marking duplicates, consolidating information, and keeping it all up to date.
10. All Issue Links have a grey line between them. There's also a longer grey line between different types of links, such as "duplicate", "related to", "blocks", "testing discovered", etc.
13. You can also just click on the headings (key, summary, assignee, reporter, status, etc.) to sort that way.
16. If you're not getting some notification emails, I'd suggest you check your email spam filter, and ensure that you have "[email protected]" as a permitted sender.
18. The Mojira reddit is the best place for questions or discussion about the tracker, or even extended discussion about particular issues. The jira software doesn't handle lots of links or comments very well, and some of the larger issues on the tracker load very slowly as a result. Comments should be limited to new information relevant to getting it fixed, such as new tests that demonstrate the issue, possible causes, fields that need to be updated such as the affected version, if the issue is a duplicate, etc. If people really want to have a discussion beyond that, it should be taken to reddit so that everyone watching the issue doesn't get spammed, and so the page doesn't get bogged down.
16. Wait, for tickets that I'm not allowed to edit, the edit button doesn't exist. So how is this happening for comments left by non-mods?
Issues that are hidden are security issues, issues that are closed are already resolved in some manner, but continue to be argued on, thus closing the issue 'locks' the comments section. Users can also set their own issues to private (as you can probably tell), and unless it is a security issue we'll unhide those.
We're only concerned with the latest version, although it helps the search filters when we list older ones.
There's no dedicated function, as far as I know, but you can filter issues that you created or issues that you're watching.
Your display name can be changed, your username cannot.
Normally the oldest one, but if there are already several duplicates created before we've encountered them, then the one with the best description will be used as the main one.
Invalid is for... invalid things such as feature requests or tech support. Works as Intended refers to behavior that players might deem as bugs but have been deemed features by Mojang. I don't see how they're interchangeable.
Presumably one of the default JIRA resolutions.
skipHover your mouse over the screenshot, it gives the username and time they posted it.
What grey line? If there's more than one, those appear so that they're easily read.
No, in those cases the bug the player is talking about is a different bug. It completely defeats the point of the bug tracker if one report contains 50 different bugs, people wouldn't know which bugs are fixed. The report will be updated if it is a clarification to the bug (eg. exceptions, better ways to reproduce).
They should, but human errors -> linked to different issue. When that 'root' issue is found to be a duplicate of an existing one, it gets linked, but JIRA doesn't have an efficient interface for transferring all the links to the other issue.
By default it's sorted by last update time. Yes, JIRA has its own query system to do that.
No, either Mojang employees themselves mark it as intended or we have evidence (eg. a tweet from Dinnerbone) that mentions that behavior is intended.Other times its really painfully obvious that it's intended.
Unsure about this from the user side, mods definitely can.
Unsure.
The JIRA bug tracker.
We really don't have a place for questions like this (and the JIRA bugtracker is only for issues with the software itself).