You will make it far easier on the developers if you are able to consistently reproduce the bug, and include DETAILED instructions on how to do so. If we cannot reproduce the bug, we may close the issue until it appears again. As an example, do not just say, "It crashed on me! I lost all of my work, this program sucks!" That is not an ideal bug report. You should try to reproduce the crash, and then include a detailed report, with any file attachments that assist in reproducing the problem. A good bug report would read similar to the following:
"I normally draw by blocking out an area with gray background-color spacebar characters, and then 'cutting out' from that image with a black foreground color and characters from the Alt-6 character set. When I do this, save the file and re-open it, it appears as a single gray block, with none of the black foreground characters appearing. I have attached a file which has been saved by TundraDraw that demonstrates this problem, and a file which has been saved by PabloDraw that loads correctly in TundraDraw. Thanks for all your help!"
Note the politeness. :) Remember, we are not getting paid to work on TundraDraw, we do this out of the goodness of our hearts, so a little politeness will go a long way.
Also, NEVER under any circumstance should you email or IRC message a bug report to one of the authors. It will be ignored. We don't have time to keep track of everything people have mentioned to us. If you want the bug to get fixed, you will take the time to report it on the bug tracker. If its not worth it to you to spend the two minutes required to submit a bug report using JIRA, its obviously not very important to you. Having a central list of all of the bugs is critical to the successful development of TundraDraw.