bugzilla-newer r710 - in trunk: . template/en/custom/pages

[ckirbach svn gnome org]

Author: ckirbach
Date: Sun Oct 19 15:01:56 2008
New Revision: 710
URL: http://svn.gnome.org/viewvc/bugzilla-newer?rev=710&view=rev

Log:
	* template/en/custom/pages/bug-HOWTO.html.tmpl: fix broken link 
to bug priority explanation.


Modified:
   trunk/ChangeLog
   trunk/template/en/custom/pages/bug-HOWTO.html.tmpl

Modified: trunk/template/en/custom/pages/bug-HOWTO.html.tmpl
==============================================================================
--- trunk/template/en/custom/pages/bug-HOWTO.html.tmpl	(original)
+++ trunk/template/en/custom/pages/bug-HOWTO.html.tmpl	Sun Oct 19 15:01:56 2008
@@ -120,7 +120,7 @@
 		The full list of severities is <a href="http://bugzilla.gnome.org/bug_status.html#severity";>here</a>, but in a nutshell: if it crashes the application, it should be Critical, and if it is a new feature request, it should be Wishlist. Everything else will fall in somewhere in between. 
 
 	<P><B>Priority: How important is the bug?</B><BR>
-		The full list of priorities is <a href="http://bugzilla.gnome.org/bug_status.html#priority";>here</a>, but in a nutshell: Does it happen a lot or in a big, key portion of the application? Or is it particularly embarassing? Then it is High. Urgent and Immediate should be reserved for things that block builds, or otherwise make an app fairly useless. These may also be used for things that are big build goals.
+		The full list of priorities is <a href="http://bugzilla.gnome.org/page.cgi?id=bug-status.html#priority";>here</a>, but in a nutshell: Does it happen a lot or in a big, key portion of the application? Or is it particularly embarassing? Then it is High. Urgent and Immediate should be reserved for things that block builds, or otherwise make an app fairly useless. These may also be used for things that are big build goals.
 
 	<P><B>Assigned To: Which developer should be responsible for fixing this bug?</B><BR>
 		Bugzilla will automatically assign the bug to a default developer upon submitting a bug report; the text box exists to allow you to manually assign it to a different developer. (To see the list of default developers for each component, click on the Component link.)