[G2 Original Android Development] dr4stic:
Submitting Bug Reports

Some of you may see me doing something new. I'm referring people to make bug reports in the official Jira. I'm creating this post as a reference point for the moment, I'll be updating it in the coming hours, but I needed a link for the FAQ entry. Thanks for your patience. I'm still fleshing out this procedure :)

What to do when you think you have a bug

First things first, you should search this thread, and then search it again before asking questions about a bug you may or may not have. Having to constantly answer the same questions about the same problem is annoying and really bothers many of the veterans on this thread. Please, search before you post.

If you can't find your issue, then post your question. Be VERY descriptive. A report of an issue or bug really needs to have, at a minimum, 3 things:

The problem you think you're seeing

The scenario required to trigger and/or reproduce the problem

Your device and ROM details (model number, nightly or rom version you experienced it on, ANY and ALL mods you've done to your system)

The most important thing is to be descriptive. I can't stress that enough. The steps required to trigger or reproduce the problem is also very important. Too many people report problems with absolutely no context or instructions and they get ignored because we can't verify that the issue really exists. It also makes it easier for others to spot problems in the procedure that could produce the bug because the user is actually reporting expected behavior and thinking that it's a bug. And that last one, telling us EVERYTHING about your device is very important as well. At least a few times bugs have been model specific.

Filing the bug report

The procedure to follow for filing a bug report can be found at the CyanogenMod "Support" Wiki entry. Please follow them in order to file a bug report.

The following fields should be set to these values if you want to get them noticed within a reasonable timeframe:

"Project" field: For bug reports against a nightly, please leave this field set to "Nightly Regressions (NIGHTLIES)". For bugs with a SNAPSHOT (stable release), set the field to "CyanogenMod (CYAN)".

"Summary" field: Keep it specific, short and sweet. It doesn't need to sound like a perfectly worded sentence to get the point across. For example "Bootloop after applying nightly with crypto kernel patches" would work just fine.

"Affect's Versions" field: Should likely be set to "cm-13.0"

Please be as descriptive as possible. Include the three things we talked about above: the problem, how to reproduce it, and any mods you might have on your system. And be as detailed as you can be. The more detail you can provide about your issue and how to reproduce it, the more likely it is someone will bother to try and fix it. Finally, please make sure to take a log and supply it on the ticket.

Why this change in reporting procedure?

You may be wondering "Why do we have to do this now, do you hate us?" ... Yes. Yes, I hate you all. But don't feel bad, I hate everyone. It's my default emotion towards people.

The truth is it's what the procedure should've been from the beginning. After some heated discussions with the Devs a few days ago (some might call it an argument, others might call it a good natured ribbing!), it seems a line has been drawn in the sand over where bug reports come from and how they're reported. Instead of me chatting to a specific dev and then having that dev conveniently forget everything I told him a week later, we'll be filing official Jira bug reports.

Part of this is my fault. I set up this thread to try and act as a reasonable interface to the more noobish of our device and to concentrate conversation for our dwindling community. Because of this, the attention this thread gets has made it the defacto "help, this is broken" place on XDA for CM on the G2. And XDA is not considered an official venue for bug reporting by CM. What I *should* have been doing was reporting the bugs here in Jira and following procedure from there. I'll be trying to handle the situation better, which is why I am writing this post.