Jump to content

Bug Report Guidelines - Please read before posting


Josh
 Share

Recommended Posts

More than 700 bug reports have been solved through this system. When choosing what to work on, my goal is to keep the lowest number of unsolved reports in the system at all times. Therefore, I typically look for the issues I am most likely to be able to solve the fastest.

What will get your bug report prioritized

  • A simple code example that demonstrates a problem and does not require any additional files will always get looked at first. This isn't always possible, so if additional files are required please make sure I have access to them.

What will get your bug report moved to the back

  • If I have to try to recreate the situation you are describing, it is very likely I will not be able to. A working example of the problem is very important, or at least precise instructions on exactly what I should do to make the problem occur.
  • If you hijack someone else's thread to add your own bug reports, or mention an unrelated bug in another topic, I won't be able to keep track of it and it will very likely be lost.
  • If you reply to a thread that has been marked as solved, there is a good chance I will lose track of it unless I immediately mark it as unsolved. Once a thread is marked solved and the forum system no longer shows it as unread to me, it is lost among 50+ pages of solved threads and I will never see it again.
  • Threads that contain a collection of bug reports, unless they are very closely related, will always be lowest priority because it is unlikely I will be able to solve all them immediately, so I will focus on another issue I can solve right away.

I tend to do bug fixes in rounds. If you don't get a response right away, don't worry. If you send me a private message or write something on Discord, there is no way I will remember it, but as long as there is a thread in this forum that is not marked as solved, I will see it during the next round of fixes.

You can filter this forum to just look at unsolved threads. This is how I keep track of what is left to work on. Even if your thread is several pages back, as long as it is not marked as solved, I will keep coming back to it.

Sometimes I will need additional information or clarification. I usually wait about a week, and if my response goes unanswered, issues will be closed due to the lack of information.

There is a lot of information to keep track of, and keeping communication as clear as possible helps me to solve issues faster. Thank you for your participation!

  • Like 2

My job is to make tools you love, with the features you want, and performance you can't live without.

Link to comment
Share on other sites

  • Josh changed the title to Bug Report Guidelines - Please read before posting
  • Josh pinned and unfeatured this topic
Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...