Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 299376 Details for
Bug 406431
3.33: Guided Bug Entry
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
[patch]
Patch to update guided bug entry for Red Hat content
guided_bug_entry.patch (text/plain), 18.67 KB, created by
David Lawrence
on 2008-03-27 18:30:06 UTC
(
hide
)
Description:
Patch to update guided bug entry for Red Hat content
Filename:
MIME Type:
Creator:
David Lawrence
Created:
2008-03-27 18:30:06 UTC
Size:
18.67 KB
patch
obsolete
>? bugzilla-3.2rh-20080327.1.tar.gz >? bugzilla.spec >? patches >Index: template/en/default/bug/create/comment-guided.txt.tmpl >=================================================================== >RCS file: /cvs/qa/rh_bugzilla_3/template/en/default/bug/create/comment-guided.txt.tmpl,v >retrieving revision 1.1.1.1 >diff -u -r1.1.1.1 comment-guided.txt.tmpl >--- template/en/default/bug/create/comment-guided.txt.tmpl 19 Nov 2007 22:11:21 -0000 1.1.1.1 >+++ template/en/default/bug/create/comment-guided.txt.tmpl 27 Mar 2008 18:27:17 -0000 >@@ -28,7 +28,6 @@ > [% USE Bugzilla %] > [% cgi = Bugzilla.cgi %] > User-Agent: [%+ cgi.user_agent() %] >-Build Identifier: [%+ cgi.param("buildid") %] > > [%+ cgi.param("comment") IF cgi.param("comment") %] > >Index: template/en/default/bug/create/create-guided.html.tmpl >=================================================================== >RCS file: /cvs/qa/rh_bugzilla_3/template/en/default/bug/create/create-guided.html.tmpl,v >retrieving revision 1.3 >diff -u -r1.3 create-guided.html.tmpl >--- template/en/default/bug/create/create-guided.html.tmpl 19 Dec 2007 16:20:59 -0000 1.3 >+++ template/en/default/bug/create/create-guided.html.tmpl 27 Mar 2008 18:27:17 -0000 >@@ -34,16 +34,28 @@ > style = "#somebugs { width: 100%; height: 500px }" > %] > >+<b>What is a [% terms.bug %]?</b> >+ > <p> >- <font color="red"> >- This is a template used on mozilla.org. This template, and the >- comment-guided.txt.tmpl template that formats the data submitted via >- the form in this template, are included as a demo of what it's >- possible to do with custom templates in general, and custom [% terms.bug %] >- entry templates in particular. As much of the text will not apply, >- you should alter it >- if you want to use this form on your [% terms.Bugzilla %] installation. >- </font> >+A [% terms.bug %] can be quickly identified as a problem with existing >+software. However, it is much more complicated than that. It can be >+a behavioural problem in an application or program that does not work at >+all. It even applies to documentation that is incorrect. >+</p> >+ >+<b>Why should you use this form?</b> >+ >+<p> >+Entering a [% terms.bug %] in this application prompts you for information that is essential to the >+developers. The information you provide will allow the developers to understand the >+behaviour you are seeing, reproduce the behaviour, and assist in getting the problem >+solved. Being able to understand and reproduce [% terms.bugs %] are the first steps >+towards getting the [% term.bug %] fixed.<br> >+<br> >+Please do <u>not</u> report [% terms.bugs %] in >+other places, such as in newsgroups or on IRC. [% terms.Bugzilla %] is the only >+reliable tracking system for Red Hat products. Red Hat cannot guarantee >+your [% terms.bug %] will be fixed unless it is reported correctly. > </p> > > [% tablecolour = "#FFFFCC" %] >@@ -71,38 +83,16 @@ > > [% IF cgi.user_agent('Netscape(\d)') %] > [% matches = cgi.user_agent().match('Netscape(\d)') %] >- <div style="background-color: lightgrey; >- border: 1px solid black; >- padding: 2px"> >- <font color="#990000"> >- <b> >- You are using Netscape [% matches.0 %]. >- Report [% terms.bugs %] with this browser to the >- <a href="http://home.netscape.com/browsers/[% matches.0 %]/feedback/index.html"> >- Netscape [% matches.0 %] Feedback Center.</a> >- </b> >- </font> >- This form is only for reporting [% terms.bugs %] in the Mozilla web browser >- and other products from mozilla.org. To report [% terms.abug %] you find >- in Netscape [% matches.0 %] with this form, you must reproduce it first in >- a recent build of >- <a href="http://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/latest/">Mozilla</a>, >- <a href="http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/">Firefox</a>, >-<a href="http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-trunk/">Thunderbird</a> or >- <a href="http://ftp.mozilla.org/pub/mozilla.org/camino/nightly/latest/">Camino</a> >- to make sure the problem hasn't been fixed already. >- </div> > [% END %] > > [% IF cgi.user_agent('Gecko/') %] > [% matches = cgi.user_agent().match('Gecko/(\d+)') %] >- > [% END %] > > <!-- @@@ Need UA checking here --> > > <a name="step1"></a> >-<h3>Step 1 of 3 - has your [% terms.bug %] already been reported?</h3> >+<h3>Step 1 of 3 - Has your [% terms.bug %] already been reported?</h3> > > <p> > <font color="red">Please don't skip this step - half of all >@@ -111,14 +101,7 @@ > Check the two lists of frequently-reported [% terms.bugs %]: > </p> > >-[%# Include other products if sensible %] >-[% IF product.name == "Firefox" %] >- [% productstring = "product=Mozilla%20Application%20Suite&product=Firefox" %] >-[% ELSIF product.name == "Thunderbird" %] >- [% productstring = "product=Mozilla%20Application%20Suite&product=Thunderbird" %] >-[% ELSE %] >- [% productstring = BLOCK %]product=[% product.name FILTER url_quote %][% END %] >-[% END %] >+[% productstring = BLOCK %]product=[% product.name FILTER url_quote %][% END %] > > <p> > <a href="duplicates.cgi?[% productstring %]&format=simple" target="somebugs">All-time Top 100</a> (loaded initially) | >@@ -143,16 +126,6 @@ > <input type="hidden" name="order" value="relevance desc"> > <input type="hidden" name="bug_status" value="__all__"> > <input type="hidden" name="product" value="[% product.name FILTER html %]"> >- [% IF product.name == "Firefox" OR >- product.name == "Thunderbird" OR >- product.name == "Mozilla Application Suite" OR >- product.name == "Camino" %] >- <input type="hidden" name="product" value="Core"> >- <input type="hidden" name="product" value="Toolkit"> >- <input type="hidden" name="product" value="PSM"> >- <input type="hidden" name="product" value="NSPR"> >- <input type="hidden" name="product" value="NSS"> >- [% END %] > <input type="hidden" name="chfieldfrom" value="-6m"> > <input type="hidden" name="chfieldto" value="Now"> > <input type="hidden" name="chfield" value="[Bug creation]"> >@@ -171,7 +144,7 @@ > > > <a name="step2"></a> >-<h3>Step 2 of 3 - give information</h3> >+<h3>Step 2 of 3 - Give detailed information</h3> > > <p> > If you've tried a few searches and your [% terms.bug %] really isn't in >@@ -181,10 +154,9 @@ > <form method="post" action="post_bug.cgi"> > <input type="hidden" name="format" value="guided"> > <input type="hidden" name="assigned_to" value=""> >+ <input type="hidden" name="op_sys" value="Linux"> > <input type="hidden" name="priority" > value="[% default.priority FILTER html %]"> >- <input type="hidden" name="version" >- value="[% default.version FILTER html %]"> > <input type="hidden" name="token" value="[% token FILTER html %]"> > > <table valign="top" cellpadding="5" cellspacing="5" border="0"> >@@ -235,67 +207,92 @@ > </td> > </tr> > </table> >- >+ <p> >+ This is the hard part due to the large number of components available to select. Here are >+ some tips on picking the right component. >+ </p> >+ <p> >+ If you are reporting a bug against the <font color="red">Red Hat Enterprise Linux</font> >+ or <font color="red">Fedora</font> line of products you can normally determine the >+ component by running<br/> >+ <br/> >+ <code>rpm -qif <i>binary name</i></code><br/> >+ <br/> >+ on the binary that you need to report the bug against. The component name will >+ be the line noted as Source RPM: but leaving the version number information off. >+ </p> >+ <p> >+ The Red Hat Install process is a special case from the normal selection of components >+ so if the bug is related to the install process, then choose <b>Anaconda</b> from >+ the component selection box. >+ </p> >+ <p> >+ If you still can't decide, select a component from the list below, and the description >+ of the component will appear in the text box to the right. >+ </p> > <p> > The area where the problem occurs. > To pick the right component, you could use the same one as > similar [% terms.bugs %] you found in your search, or read the full list of > <a target="_blank" href="describecomponents.cgi?product= >- [% product.name FILTER url_quote %]">component >- descriptions</a> (opens in new window) if you need more help. >+ [% product.name FILTER url_quote %]">component >+ descriptions</a> (opens in new window) if you need more help. > </p> > </td> > </tr> > >- [%# We override rep_platform and op_sys for simplicity. The values chosen >- are based on which are most common in the b.m.o database %] >- [% rep_platform = [ "PC", "Macintosh", "All", "Other" ] %] >- > <tr bgcolor="[% tablecolour %]"> > <td align="right" valign="top"> >- <b>Hardware Platform</b> >- </td> >- <td valign="top"> >- [% PROCESS select sel = 'rep_platform' %] >- </td> >- </tr> >- >- [% op_sys = [ "Windows 98", "Windows NT", "Windows 2000", "Windows XP", >- "Mac System 9.x", "MacOS X", >- "Linux", "All", "other" ] %] >- >- <tr> >- <td align="right" valign="top"> >- <b>Operating System</b> >+ <b>Version</b> > </td> > <td valign="top"> >- [% PROCESS select sel = 'op_sys' %] >+ <select name="version" id="version" size="5"> >+ [% FOREACH v = product.versions %] >+ <option value="[% v.name FILTER html %]" >+ [% " selected=\"selected\"" IF v.name == default.version %]> >+ [% v.name FILTER html %] >+ </option> >+ [% END %] >+ </select> >+ <p> >+ Before, you selected a product. Now choose the proper version of that product. For example, >+ if you are reporting a bug for Red Hat Enterprise Linux 3 then choose 3 as the version. >+ </p> >+ <p> >+ If you are reporting a bug against a <font color="red">Red Hat Enterprise Linux</font> >+ product and are unsure of the version of product you are using, you can run<br/> >+ <br/> >+ cat /etc/redhat-release<br/> >+ <br/> >+ and choose the version number reported by the output. Beta versions >+ are usually not numbered this way so would not apply. Then just choose 'beta'. >+ </p> >+ <p> >+ If there is only one choice of version then simply select the single choice. >+ </p> > </td> > </tr> > >- [% IF product.name.match("Firefox|Camino|Mozilla Application Suite") %] >- [% matches = cgi.user_agent('Gecko/(\d+)') %] >- [% buildid = cgi.user_agent() IF matches %] >- [% END %] >- >- [%# Accept URL parameter build ID for non-browser products %] >- [% IF cgi.param("buildid") %] >- [% buildid = cgi.param("buildid") %] >- [% END %] >- > <tr bgcolor="[% tablecolour %]"> > <td align="right" valign="top"> >- <b>Build Identifier</b> >+ <b>Hardware Platform</b> > </td> > <td valign="top"> >- <input type="text" size="80" name="buildid" value="[% buildid FILTER html %]"> >+ [% PROCESS select sel = 'rep_platform' %] >+ <p> >+ If you are unsure of the architecture choice, then you can run<br> >+ <br> >+ uname -m<br> >+ <br> >+ and choose the one the best matches one from the selection box.<br> >+ </p> > <p> >- This should identify the exact version of the product you were using. >- If the above field is blank or you know it is incorrect, copy the >- version text from the product's Help | >- About menu (for browsers this will begin with "Mozilla/5.0..."). >- If the product won't start, instead paste the complete URL you downloaded >- it from. >+ For Intel compatible systems such as for AMD and Cyrix processors please >+ choose i386 as the architecture. >+ </p> >+ <p> >+ If the product you chose is not relevant to any particular architecture such as >+ Red Hat Web Site, etc. then just choose All. > </p> > </td> > </tr> >@@ -328,12 +325,10 @@ > </p> > <p> > <tt> >- <font color="#990000">Bad example</font>: mail crashed >+ <font color="#990000">Bad</font>: Installer crashed > </tt> >- <br> > <tt> >- <font color="#009900">Good example</font>: >- crash if I close the mail window while checking for new POP mail >+ <font color="#009900">Good</font>: Installer hangs when loading aic7xxx module > </tt> > </p> > </td> >@@ -354,18 +349,22 @@ > as specific as possible about what is wrong. > </p> > <p> >+ Examples:<br/> > <tt> >- <font color="#990000">Bad example</font>: Mozilla crashed. >- You suck! >+ <font color="#990000">Bad</font>: The program simply will not work. > </tt> >- <br> >+ <br/> > <tt> >- <font color="#009900">Good example</font>: After a crash which >- happened when I was sorting in the Bookmark Manager,<br> all of my >- top-level bookmark folders beginning with the letters Q to Z are >- no longer present. >+ <font color="#009900">Good</font>: When I use a particular option to the 'ls' >+ command, I do not get the proper output as expected. The option I was trying >+ was trying was <i>blah</i> and the exact output was <i>blah</i>. > </tt> > </p> >+ <p> >+ <b>Note:</b> If you need to enter large amounts of text such as logfiles, sample code, patches, etc. >+ then please submit them as an attachment to the [% terms.bug %] instead of placing them in the description >+ field. You will be given the opportunity to make attachments after submitting the [% terms.bug %] report. >+ </p> > </td> > </tr> > >@@ -452,23 +451,14 @@ > cols = constants.COMMENT_COLS > %] > <p> >- Add any additional information you feel may be >- relevant to this [% terms.bug %], such as the <b>theme</b> you were >- using (does the [% terms.bug %] still occur >- with the default theme?), a >- <b><a href="http://kb.mozillazine.org/Quality_Feedback_Agent">Talkback crash ID</a></b>, or special >- information about <b>your computer's configuration</b>. Any information >- longer than a few lines, such as a <b>stack trace</b> or <b>HTML >- testcase</b>, should be added >- using the "Create a new Attachment" link on the [% terms.bug %], after >- it is filed. If you believe that it's relevant, please also include >- your build configuration, obtained by typing <tt>about:buildconfig</tt> >- into your URL bar. >- <br> >- <br> >- If you are reporting a crash, note the module in >- which the software crashed (e.g., <tt>Application Violation in >- gkhtml.dll</tt>). >+ Add any additional information you feel may be relevant to this bug, such >+ as a few lines of output showing the error message, binary's version number, >+ or special information about your computer's configuration. >+ </p> >+ <p> >+ Any information longer than a few lines, such as a <b>stack trace</b> or >+ <b>patch</b>, should be added using the "Create a new Attachment" link on >+ the [% terms.bug %], after it is filed. > </p> > </td> > </tr> >@@ -479,25 +469,17 @@ > </td> > <td valign="top"> > <select name="bug_severity"> >- <option name="critical" value="critical"> >- Critical: The software crashes, hangs, or causes you to >- lose data. >- </option> >- <option name="major" value="major"> >- Major: A major feature is broken. >+ <option name="urgent" value="urgent"> >+ Urgent: The software crashes, hangs, or causes you to lose data. > </option> >- <option name="normal" value="normal" selected="selected"> >- Normal: It's [% terms.abug %] that should be fixed. >+ <option name="high" value="high"> >+ High: A major feature is broken. > </option> >- <option name="minor" value="minor"> >- Minor: Minor loss of function, and there's an easy workaround. >+ <option name="medium" value="medium" selected="selected"> >+ Medium: It's [% terms.abug %] that should be fixed. > </option> >- <option name="trivial" value="trivial"> >- Trivial: A cosmetic problem, such as a misspelled word or >- misaligned text. >- </option> >- <option name="enhancement" value="enhancement"> >- Enhancement: Request for new feature or enhancement. >+ <option name="low" value="low"> >+ Low: Minor loss of function or cosmetic problem. There's an easy workaround. > </option> > </select> > <p> >@@ -506,11 +488,31 @@ > </p> > </td> > </tr> >+ >+ <tr> >+ <td valign="top" align="right"> >+ <b>Security</b> >+ </td> >+ <td valign="top"> >+ <input type="checkbox" name="bit-71" value="1"> This report is security sensitive. >+ <p> >+ Red Hat takes security very seriously and we aim to take immediate action to address >+ any security related problems that involve our products or services. >+ You should check this if: >+ <ul> >+ <li>If you have found a security vulnerability with a Red Hat product or service</li> >+ <li>If you are unsure about how a known vulnerability affects a Red Hat product or service</li> >+ </ul> >+ Alternatively, you may email the information to <a href="mailto:secalert@redhat.com">secalert@redhat.com</a>. >+ You can communicate with us securely using <a href="http://www.redhat.com/security/team/key/">our GPG key</a>. >+ </p> >+ </td> >+ </tr> > </table> > > > <a name="step3"></a> >-<h3>Step 3 of 3 - submit the [% terms.bug %] report</h3> >+<h3>Step 3 of 3 - Submit the [% terms.bug %] report</h3> > > <p> > <input type="submit" id="report" value=" Submit [% terms.Bug %] Report " >Index: template/en/default/bug/create/user-message.html.tmpl >=================================================================== >RCS file: /cvs/qa/rh_bugzilla_3/template/en/default/bug/create/user-message.html.tmpl,v >retrieving revision 1.1.1.1 >diff -u -r1.1.1.1 user-message.html.tmpl >--- template/en/default/bug/create/user-message.html.tmpl 19 Nov 2007 22:11:21 -0000 1.1.1.1 >+++ template/en/default/bug/create/user-message.html.tmpl 27 Mar 2008 18:27:17 -0000 >@@ -34,3 +34,10 @@ > [% terms.bug %] writing guidelines</a>, please look at the list of > <a href="duplicates.cgi">most frequently reported [% terms.bugs %]</a>, and please > <a href="query.cgi">search</a> for the [% terms.bug %]. >+ >+[%# REDHAT EXTENSION START 406431 %] >+<p> >+ You may also use the <a href="enter_bug.cgi?format=guided&product=[% product.name FILTER url_quote %]"> >+ Guided</a> [% terms.bug %] entry page for a easier step by step method. >+</p> >+[%# REDHAT EXTENSION END 406431 %]
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Flags:
nelhawar
: review+
dkl
: review? (
kbaker
)
Actions:
View
|
Diff
Attachments on
bug 406431
: 299376