[Bug 777874] Re: If multiple reports on new bug, mark it confirmed

An API script which will confirm any New bugs with the same criteria is available in lp:~flacoste/+junk/lp-bugs-tools. It's lp-auto-confirm.py -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/777874 Titl

[Bug 777874] Re: If multiple reports on new bug, mark it confirmed

This is fix-released for Launchpad. We will remove either the feature flags or the functionality based on the discussion Matthew Revell and Kate have about this. That is tracked separately in bug 820442. ** Changed in: launchpad Status: Fix Committed => Fix Released -- You received this

[Bug 777874] Re: If multiple reports on new bug, mark it confirmed

@Kate, it would be possible to write an API script to migrate all historical bugs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/777874 Title: If multiple reports on new bug, mark it confirmed To m

[Bug 777874] Re: If multiple reports on new bug, mark it confirmed

@Kate: I've marked the statuses as you suggest. You are correct, this will not address historical "New" bug tasks that already have multiple people affected--but even for these old bugs, the first time a new person is affected, the code will be triggered and the status will move to "Confirmed". *

[Bug 777874] Re: If multiple reports on new bug, mark it confirmed

I'm thinking that the status should be Fix Released for Ubuntu, and Fix Committed for the general problem, shouldn't it? Also, just to confirm, this will trigger from now on, but won't address the historical ones? (and THANK YOU!!! for getting it in) -- You received this bug notification b

[Bug 777874] Re: If multiple reports on new bug, mark it confirmed

I'm not quite sure on whether "Fix Released" is appropriate once we have this released exclusively to ubuntu and launchpad (feature flaged), but that's where we are, and that's what I'm doing. Ubuntu should now have the requested behavior. ** Changed in: launchpad Status: Fix Committed =>

[Bug 777874] Re: If multiple reports on new bug, mark it confirmed

This should be rolled out now. Not sure if you want to mark it as 'fix released' until you set the feature flags, so I am not touching it :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/777874 Title:

[Bug 777874] Re: If multiple reports on new bug, mark it confirmed

This is ready for deployment (and should be deployed in the next four hours). In order to turn on the behavior for ubuntu and launchpad, we will need to add these feature rules: bugs.autoconfirm.enabled_distribution_names default 1 ubuntu bugs.autoconfirm.enabled_product_names default

[Bug 777874] Re: If multiple reports on new bug, mark it confirmed

** Tags removed: qa-needstesting ** Tags added: qa-ok -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/777874 Title: If multiple reports on new bug, mark it confirmed To manage notifications about thi

[Bug 777874] Re: If multiple reports on new bug, mark it confirmed

Fixed in stable r13470 . ** Tags added: qa-needstesting ** Changed in: launchpad Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subsc

[Bug 777874] Re: If multiple reports on new bug, mark it confirmed

** Branch linked: lp:~gary/launchpad/bug777874 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/777874 Title: If multiple reports on new bug, mark it confirmed To manage notifications about this bug g

[Bug 777874] Re: If multiple reports on new bug, mark it confirmed

I have a branch in which this is all working. The last step is to make adding a bug duplicate or saying "me too" via AJAX automatically update the bugtask statuses. I hope to do that tomorrow. If I don't have it working in a few hours, I will land a branch with the server-side functionality for

Re: [Bug 777874] Re: If multiple reports on new bug, mark it confirmed

> The problem is that feature flags are for page context. [aside] That's generally true at the moment, but it's not the intention. We have flags that are used in cron scripts (iirc) and soon we will have flags active for incoming email. It makes sense to have flags that can be turned on and off

[Bug 777874] Re: If multiple reports on new bug, mark it confirmed

In regards to the feature flag, I had considered that general approach. The problem is that feature flags are for page context. That's not what we are interested in here: we are interested in bug tasks. For any bug modified, we will need to iterate over its bug tasks to see if the bug is pertinen

Re: [Bug 777874] Re: If multiple reports on new bug, mark it confirmed

On Thu, Jul 14, 2011 at 11:47 AM, Martin Pool wrote: > Perhaps the flag scopes should be "distribution:ubuntu" and > "project:bzr" just to be a little more clear. We have a single unified top levelnamespace, it would be overly precise to insist on type safety there. -- You received this bug not

Re: [Bug 777874] Re: If multiple reports on new bug, mark it confirmed

In implementation, please think about how the change of status will be represented in the web ui and in email notifications. If it looks like the particular user that checked 'affects' also changed the status that might cause some confusion. Perhaps the flag scopes should be "distribution:ubuntu"

Re: [Bug 777874] Re: If multiple reports on new bug, mark it confirmed

On Thu, Jul 14, 2011 at 6:43 AM, Francis J. Lacoste <777...@bugs.launchpad.net> wrote: > I'd rather suggest a boolean feature flag and then we use a custom scope > selector. +1 > The scope handler (project:?) could take a comma list of > project names. I'd start with (perhaps pillar:) taking jus

[Bug 777874] Re: If multiple reports on new bug, mark it confirmed

I'd rather suggest a boolean feature flag and then we use a custom scope selector. The scope handler (project:?) could take a comma list of project names. That way we don't need custom flag parsing logic in the feature, and we have a reusable feature scope! -- You received this bug notification

[Bug 777874] Re: If multiple reports on new bug, mark it confirmed

We know Ubuntu wants this behavior. We are less confident that other projects will. Francis suggested feature flags as an initial cut for a distinguishing mechanism. I think we could do this by, for instance, looking for a feature flag that specifies a comma-separated whitelist of projects that w

[Bug 777874] Re: If multiple reports on new bug, mark it confirmed

** Changed in: launchpad Assignee: (unassigned) => Gary Poster (gary) ** Changed in: launchpad Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/777874 Title:

[Bug 777874] Re: If multiple reports on new bug, mark it confirmed

** Changed in: ubuntu Milestone: oneiric-alpha-2 => oneiric-alpha-3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/777874 Title: If multiple reports on new bug, mark it confirmed To manage notif

[Bug 777874] Re: If multiple reports on new bug, mark it confirmed

Would like to see this deployed before Alpha 3 (Aug 4th) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/777874 Title: If multiple reports on new bug, mark it confirmed To manage notifications about

[Bug 777874] Re: If multiple reports on new bug, mark it confirmed

Escalated by Kate on the stakeholders mailing list. ** Changed in: launchpad Importance: Low => Critical ** Tags added: escalated -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/777874 Title: If

[Bug 777874] Re: If multiple reports on new bug, mark it confirmed

** Tags added: bug-lifecycle -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/777874 Title: If multiple reports on new bug, mark it confirmed To manage notifications about this bug go to: https://bugs

[Bug 777874] Re: If multiple reports on new bug, mark it confirmed

I agree with robert that the confirmed/triaged workflow could benefit from some additional thinking. There's actually two separate problems here, as I see it. First, the core problem I think Kate is trying to get at is that the volume of bug reports to Ubuntu is very high, well beyond the availab

[Bug 777874] Re: If multiple reports on new bug, mark it confirmed

** Changed in: ubuntu Milestone: oneiric-alpha-1 => oneiric-alpha-2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/777874 Title: If multiple reports on new bug, mark it confirmed -- ubuntu-bugs

[Bug 777874] Re: If multiple reports on new bug, mark it confirmed

** Tags added: ubuntu-platform -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/777874 Title: If multiple reports on new bug, mark it confirmed -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.co

[Bug 777874] Re: If multiple reports on new bug, mark it confirmed

While this may be low from a Launchpad perspective, its pretty high to get things efficient in the Ubuntu project. Adding a task related to Ubuntu, and indicating our importance on this. ** Also affects: ubuntu Importance: Undecided Status: New ** Changed in: ubuntu Status: New