<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>bug on Launchpad Blog</title>
    <link>https://blog.launchpad.net/tags/bug/</link>
    <description>News and updates from the Launchpad team</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 04 Oct 2011 07:12:35 +0000</lastBuildDate>
    <atom:link href="https://blog.launchpad.net/feed/tags/bug/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Finding bugs that affect you</title>
      <link>https://blog.launchpad.net/general/finding-bugs-that-affect-you/</link>
      <pubDate>Tue, 04 Oct 2011 07:12:35 +0000</pubDate>
      <dc:creator>Martin Pool</dc:creator>
      <guid isPermaLink="false">https://blog.launchpad.net/?p=2890</guid>
      <description>&lt;p&gt;We&amp;rsquo;ve recently deployed two features that make it easier to find bugs that you&amp;rsquo;re previously said affect you:&lt;/p&gt;
&lt;p&gt;1: On your &lt;a href=&#34;https://bugs.launchpad.net/~&#34;&gt;personal bugs page&lt;/a&gt;, there&amp;rsquo;s now an &lt;a href=&#34;https://bugs.launchpad.net/~/+affectingbugs&#34;&gt;&lt;strong&gt;Affecting bugs&lt;/strong&gt;&lt;/a&gt; that shows all these bugs.&lt;/p&gt;
&lt;p&gt;2: On a project, distribution or source package bug listing page, there&amp;rsquo;s now a &lt;strong&gt;&amp;ldquo;Bugs affecting me&amp;rdquo;&lt;/strong&gt; filter on the right (for example, &lt;a href=&#34;https://bugs.launchpad.net/launchpad/+bugs?search=Search&amp;amp;field.affects_me=on&amp;amp;orderby=-date_last_updated&#34;&gt;bugs affecting you in the Launchpad product&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;Counts of the number of affected users already help developers know which bugs are most urgent to fix, both directly and by feeding into Launchpad&amp;rsquo;s &lt;a href=&#34;http://blog.launchpad.net/bug-tracking/bug-heat&#34;&gt;bug heat heuristic&lt;/a&gt;.  With these changes, the &amp;ldquo;affects me&amp;rdquo; feature will also make it easier for you to keep an eye on these bugs, without having to subscribe to all mail from them.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://blog.launchpad.net/images/posts/2011/09/20110930_002.png&#34;&gt;&lt;img src=&#34;https://blog.launchpad.net/images/posts/2011/09/20110930_002.png&#34; alt=&#34;screenshot of &amp;ldquo;This bug affects me&amp;rdquo; control&#34;&gt;&lt;/a&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>team owner no longer implies team member</title>
      <link>https://blog.launchpad.net/coming-features/team-owner-no-longer-implies-team-member/</link>
      <pubDate>Tue, 31 May 2011 08:14:01 +0000</pubDate>
      <dc:creator>Robert Collins</dc:creator>
      <guid isPermaLink="false">https://blog.launchpad.net/?p=2539</guid>
      <description>&lt;p&gt;A short headsup about an upcoming change.&lt;/p&gt;
&lt;p&gt;A very long time ago the team owner was always a team member. This was changed to make team owners optionally members (sometime before 2008!). However the change was incomplete - there has been an inconsistency in the codebase ever since. For the details see &lt;a href=&#34;https://bugs.launchpad.net/launchpad/+bug/227494&#34;&gt;bug 227494&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;I wanted to let everyone know about us actually finishing this change though, because for a small number of teams (about 400) their administrators may be surprised when they cannot do things.&lt;/p&gt;
&lt;p&gt;The inconsistency was this: if a team owner leaves the team, so they just own it, then they are not listed as a team member. But if they try to exercise a privilege the team grants - e.g. if the team is a bug supervisor - the team owners were able to do this. This setup made it impossible for users to accurately determine who can carry out the responsibilities of a team : the Launchpad web UI incorrectly reported team members.&lt;/p&gt;
&lt;p&gt;The fix which will be deployed in the next day or so corrects this inconsistency: Team ownership will no longer grant access to anything that team membership grants.&lt;/p&gt;
&lt;p&gt;For clarity, these are the rules around team owners:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;When a team owner is assigned (or a team made) the owner defaults to being an administrator-member.&lt;/li&gt;
&lt;li&gt;If a team owner deactivates their team membership then they are not considered a team member anymore: resources and access that team membership grants will not be available to the owner at this point.&lt;/li&gt;
&lt;li&gt;Team owners can always perform adminstrative tasks on the team: creating new administrators, edit the team description, rename the team etc.&lt;/li&gt;
&lt;li&gt;Point 3 allows an owner to add themself to the team they own even if they deactivated their membership previously.&lt;/li&gt;
&lt;/ol&gt;
</description>
    </item>
    
    <item>
      <title>Should bug search match target names?</title>
      <link>https://blog.launchpad.net/bug-tracking/do-you-think-bug-search-should-match-target-names/</link>
      <pubDate>Mon, 07 Feb 2011 01:15:34 +0000</pubDate>
      <dc:creator>Robert Collins</dc:creator>
      <guid isPermaLink="false">https://blog.launchpad.net/?p=1914</guid>
      <description>&lt;p&gt;We have a small quandry on the Launchpad development team at the moment. As &lt;a href=&#34;https://bugs.launchpad.net/bugs/268508&#34;&gt;bug 268508&lt;/a&gt; discusses, when one searches for a bug on Launchpad we do a substring search on the names of bug targets.&lt;/p&gt;
&lt;p&gt;For instance, searching in Ubuntu for &amp;lsquo;gcc&amp;rsquo; will return all bugs on the packages &amp;lsquo;gcc&amp;rsquo;, &amp;lsquo;gcc-4.4&amp;rsquo;, &amp;lsquo;gcc-4.3&amp;rsquo;, &amp;lsquo;gcc-3.3&amp;rsquo; and so forth. Likewise search for bugs in a project group will do a similar substring search on each of the individual projects in the project group.&lt;/p&gt;
&lt;p&gt;It turns out that doing this search is itself expensive. I &lt;a href=&#34;https://lists.ubuntu.com/archives/ubuntu-devel/2011-February/032381.html&#34;&gt;asked on the Ubuntu devel&lt;/a&gt; list about turning it off. We would close bug 268508 and also significantly improve search performance.&lt;/p&gt;
&lt;p&gt;However this is a possibly contentious change - there was one mail strongly in favour of the current behaviour - so I&amp;rsquo;d like to get this change proposed to a wider community.&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;ve got a strong opinion - that the current behaviour is good, or like bug  268508 describes, that its a poor behaviour and we would be better off without it, then I&amp;rsquo;d love to hear from you. Just leave a comment on this post, drop me an email - robert at canonical.com - or post to the launchpad-users mailing list.&lt;/p&gt;
&lt;p&gt;Thanks,&lt;br&gt;
Rob (LP technical architect)&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Showing the number of affected users</title>
      <link>https://blog.launchpad.net/coming-features/showing-the-number-of-affected-users-2/</link>
      <pubDate>Tue, 15 Dec 2009 16:32:23 +0000</pubDate>
      <dc:creator>Martin Pool</dc:creator>
      <guid isPermaLink="false">https://blog.launchpad.net/?p=1222</guid>
      <description>&lt;p&gt;Gavin just landed a very welcome branch to &lt;a href=&#34;https://bugs.edge.launchpad.net/malone/+bug/494040&#34;&gt;show the number of users affected by a bug on the bug page (bug 494040)&lt;/a&gt;. You can also sort a list by the number of users affected, and &lt;a href=&#34;https://bugs.edge.launchpad.net/malone/+bugs?field.searchtext=&amp;amp;orderby=-users_affected_count&amp;amp;search=Search&amp;amp;field.status%3Alist=NEW&amp;amp;field.status%3Alist=INCOMPLETE_WITH_RESPONSE&amp;amp;field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&amp;amp;field.status%3Alist=CONFIRMED&amp;amp;field.status%3Alist=TRIAGED&amp;amp;field.status%3Alist=INPROGRESS&amp;amp;field.status%3Alist=FIXCOMMITTED&amp;amp;field.assignee=&amp;amp;field.bug_reporter=&amp;amp;field.omit_dupes=on&amp;amp;field.has_patch=&amp;amp;field.has_no_package=&#34;&gt;doing this&lt;/a&gt; shows that two other popular bugs are related: &lt;a href=&#34;https://bugs.edge.launchpad.net/malone/+bug/283539&#34;&gt;provide a list of bugs affecting a user (283539)&lt;/a&gt; and &lt;a href=&#34;https://bugs.edge.launchpad.net/malone/+bug/271332&#34;&gt;show the number of affected users in a bug list (271332)&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Needless to say, the bugs that affect the most users aren&amp;rsquo;t always the ones that should be fixed first. But it&amp;rsquo;s useful data, and more useful now that it&amp;rsquo;s easily available.&lt;/p&gt;
&lt;p&gt;You&amp;rsquo;ll be able to use this after the release of Launchpad 3.1.12 on Wednesday the 16th December or on &lt;a href=&#34;https://edge.launchpad.net&#34;&gt;Edge&lt;/a&gt; right away.&lt;/p&gt;
</description>
    </item>
    
  </channel>
</rss>
