<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Improving Bugzilla: People, Bugs, Search, and Planning</title>
	<atom:link href="http://www.azarask.in/blog/post/improving-bugzilla-people-bugs-search-and-planning/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.azarask.in/blog/post/improving-bugzilla-people-bugs-search-and-planning/</link>
	<description>-- aza &#124; ɐzɐ --</description>
	<lastBuildDate>Wed, 08 Feb 2012 10:25:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: شات</title>
		<link>http://www.azarask.in/blog/post/improving-bugzilla-people-bugs-search-and-planning/comment-page-1/#comment-14359</link>
		<dc:creator>شات</dc:creator>
		<pubDate>Thu, 09 Jun 2011 02:38:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=212#comment-14359</guid>
		<description>China wholesale beads store, free shipping, and very good post really</description>
		<content:encoded><![CDATA[<p>China wholesale beads store, free shipping, and very good post really</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: دردشة</title>
		<link>http://www.azarask.in/blog/post/improving-bugzilla-people-bugs-search-and-planning/comment-page-1/#comment-14358</link>
		<dc:creator>دردشة</dc:creator>
		<pubDate>Thu, 09 Jun 2011 02:37:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=212#comment-14358</guid>
		<description>this is vere niceee</description>
		<content:encoded><![CDATA[<p>this is vere niceee</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: basur</title>
		<link>http://www.azarask.in/blog/post/improving-bugzilla-people-bugs-search-and-planning/comment-page-1/#comment-12134</link>
		<dc:creator>basur</dc:creator>
		<pubDate>Tue, 26 Oct 2010 08:59:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=212#comment-12134</guid>
		<description>We have a bug for making the default enter_bug form simpler. It actually requires very little work at this point, but the developer assigned hasn’t done anything about it for a while.</description>
		<content:encoded><![CDATA[<p>We have a bug for making the default enter_bug form simpler. It actually requires very little work at this point, but the developer assigned hasn’t done anything about it for a while.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: بنت الكويت</title>
		<link>http://www.azarask.in/blog/post/improving-bugzilla-people-bugs-search-and-planning/comment-page-1/#comment-11950</link>
		<dc:creator>بنت الكويت</dc:creator>
		<pubDate>Sat, 02 Oct 2010 10:11:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=212#comment-11950</guid>
		<description>nice A couple of days I told a friend about this, noting that it probably will be realized on Android first.e.</description>
		<content:encoded><![CDATA[<p>nice A couple of days I told a friend about this, noting that it probably will be realized on Android first.e.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: göt sikiş</title>
		<link>http://www.azarask.in/blog/post/improving-bugzilla-people-bugs-search-and-planning/comment-page-1/#comment-11915</link>
		<dc:creator>göt sikiş</dc:creator>
		<pubDate>Fri, 01 Oct 2010 10:41:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=212#comment-11915</guid>
		<description>Max Kanat-Alexander, Alex Faaborg, Jennifer Boriss, Madhava Enros, Dave Miller,</description>
		<content:encoded><![CDATA[<p>Max Kanat-Alexander, Alex Faaborg, Jennifer Boriss, Madhava Enros, Dave Miller,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sex</title>
		<link>http://www.azarask.in/blog/post/improving-bugzilla-people-bugs-search-and-planning/comment-page-1/#comment-11364</link>
		<dc:creator>Sex</dc:creator>
		<pubDate>Tue, 07 Sep 2010 02:04:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=212#comment-11364</guid>
		<description>One really simple change I’d like to see is how form posts are handled in Bugzilla. Right now, when you make a change of any sort, say add a comment, and submit, the result of the form post is the newly updated bug. That’s convenient. That is, right up until you see an email that someone else has made a change that you want to see. The bug’s still up, so you naturally hit F5/Cmd-R to refresh the bug. The problem is that when you do this, Bugzilla tries to resubmit the last change, which you don’t want to do.</description>
		<content:encoded><![CDATA[<p>One really simple change I’d like to see is how form posts are handled in Bugzilla. Right now, when you make a change of any sort, say add a comment, and submit, the result of the form post is the newly updated bug. That’s convenient. That is, right up until you see an email that someone else has made a change that you want to see. The bug’s still up, so you naturally hit F5/Cmd-R to refresh the bug. The problem is that when you do this, Bugzilla tries to resubmit the last change, which you don’t want to do.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: porno</title>
		<link>http://www.azarask.in/blog/post/improving-bugzilla-people-bugs-search-and-planning/comment-page-1/#comment-11260</link>
		<dc:creator>porno</dc:creator>
		<pubDate>Sun, 05 Sep 2010 23:51:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=212#comment-11260</guid>
		<description>One really simple change I’d like to see is how form posts are handled in Bugzilla. Right now, when you make a change of any sort, say add a comment, and submit, the result of the form post is the newly updated bug. That’s convenient. That is, right up until you see an email that someone else has made a change that you want to see. The bug’s still up, so you naturally hit F5/Cmd-R to refresh the bug. The problem is that when you do this, Bugzilla tries to resubmit the last change, which you don’t want to do.</description>
		<content:encoded><![CDATA[<p>One really simple change I’d like to see is how form posts are handled in Bugzilla. Right now, when you make a change of any sort, say add a comment, and submit, the result of the form post is the newly updated bug. That’s convenient. That is, right up until you see an email that someone else has made a change that you want to see. The bug’s still up, so you naturally hit F5/Cmd-R to refresh the bug. The problem is that when you do this, Bugzilla tries to resubmit the last change, which you don’t want to do.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zayıflama Lida Fx15 Ve Biber Hapı Zlfvbh</title>
		<link>http://www.azarask.in/blog/post/improving-bugzilla-people-bugs-search-and-planning/comment-page-1/#comment-10263</link>
		<dc:creator>Zayıflama Lida Fx15 Ve Biber Hapı Zlfvbh</dc:creator>
		<pubDate>Wed, 21 Jul 2010 22:39:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=212#comment-10263</guid>
		<description>All these ideas sound great. Where are the notes located? Is there a project planning wiki or buglist for all these features? I’d love to follow the progress.</description>
		<content:encoded><![CDATA[<p>All these ideas sound great. Where are the notes located? Is there a project planning wiki or buglist for all these features? I’d love to follow the progress.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vinod</title>
		<link>http://www.azarask.in/blog/post/improving-bugzilla-people-bugs-search-and-planning/comment-page-1/#comment-5346</link>
		<dc:creator>Vinod</dc:creator>
		<pubDate>Thu, 14 May 2009 11:40:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=212#comment-5346</guid>
		<description>Bugzilla having all basic feature of bug tracking, I feel, all the bugs must be listed when user selects &#039;New&#039; and the relevant product/project. As this will enable user to have a look at kind of issues logged before entering his bug.

The other option would be to place &#039;New&#039; link above the bug list of desired project/product.</description>
		<content:encoded><![CDATA[<p>Bugzilla having all basic feature of bug tracking, I feel, all the bugs must be listed when user selects &#8216;New&#8217; and the relevant product/project. As this will enable user to have a look at kind of issues logged before entering his bug.</p>
<p>The other option would be to place &#8216;New&#8217; link above the bug list of desired project/product.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Benjamin Smedberg</title>
		<link>http://www.azarask.in/blog/post/improving-bugzilla-people-bugs-search-and-planning/comment-page-1/#comment-3478</link>
		<dc:creator>Benjamin Smedberg</dc:creator>
		<pubDate>Thu, 15 Jan 2009 17:31:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=212#comment-3478</guid>
		<description>Bugzilla requires everyone to make too many choices all the time.

Reduce to the absolute minimum the amount of information required/presented by bugzilla. Currently we track all kinds of fields (Os/platform/severity/priority/etc). Most of these fields are only useful occasionally, and often just get in the way or are incorrect. Rather than requiring that everyone try to fill in correct metadata all the time, only submit metadata when it&#039;s actually likely to be useful.

Also my little pet peeve: why are Status and Resolution separate fields? Ideally we&#039;d just have one status field, with a simple set of dropdowns like:

UNCO
NEW
ASSIGNED
FIXED
VERIFIED
INCOMPLETE
WORKSFORME
DUPLICATE
INVALID</description>
		<content:encoded><![CDATA[<p>Bugzilla requires everyone to make too many choices all the time.</p>
<p>Reduce to the absolute minimum the amount of information required/presented by bugzilla. Currently we track all kinds of fields (Os/platform/severity/priority/etc). Most of these fields are only useful occasionally, and often just get in the way or are incorrect. Rather than requiring that everyone try to fill in correct metadata all the time, only submit metadata when it&#8217;s actually likely to be useful.</p>
<p>Also my little pet peeve: why are Status and Resolution separate fields? Ideally we&#8217;d just have one status field, with a simple set of dropdowns like:</p>
<p>UNCO<br />
NEW<br />
ASSIGNED<br />
FIXED<br />
VERIFIED<br />
INCOMPLETE<br />
WORKSFORME<br />
DUPLICATE<br />
INVALID</p>
]]></content:encoded>
	</item>
</channel>
</rss>

