Home | History | Annotate | Download | only in source

Lines Matching full:report

1 page.title=Report Bugs
29 <h2 id="report-issues">Report Issues</h2>
33 allow anyone to see your report, which may put users at risk until the bug is
35 <p>Here's how to report <strong>non-security</strong> bugs:</p>
51 <p><a href="https://code.google.com/p/android/issues/entry?template=User%20bug%20report">Bug in your Device</a> -
55 <p><a href="https://code.google.com/p/android/issues/entry?template=Developer%20bug%20report">Bug in the Software</a> -
75 any particular release. To see what happens to your bug once you report it,
80 issue is to be resolved. Below, there are some examples of a good bug report
81 and a poor bug report.</p>
83 <h2 id="a-poor-bug-report">A Poor Bug Report</h2>
98 <p>This is a poor bug report because it doesn't provide any context for the
101 it. In other words, this bug report doesn't provide enough information for
103 <h2 id="a-good-bug-report">A Good Bug Report</h2>