incorrect results when querying for unassigned bugs

[Lee Bieber]

When i do an advanced bug search and click "Nobody" for the assignee, I get several bugs in the results that have assignees

Query is https://bugs.launchpad.net/drizzle/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&assignee_option=none&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_no_branches.used=&search=Search

Some of the bugs that show up in the list that have assignee:
https://bugs.launchpad.net/drizzle/+bug/628398
https://bugs.launchpad.net/drizzle/+bug/628860
https://bugs.launchpad.net/drizzle/+bug/628397
https://bugs.launchpad.net/drizzle/+bug/628189

[Gavin Panella (allenap)]

I think this is a problem where the bug has a project task and a
project series task. The project task defers to one of the project
series tasks for its assignee (and other things), but it seems that
searches don't take this into consideration: if the project task was
not assigned before a series task was added then it will be included
in search results.

I've attached a workaround that uses the web API. It takes a couple of
minutes to run, but perhaps it will be useful to you while we resolve
this bug.

[Gavin Panella (allenap)]

This is a very slightly more correct version of the earlier script. I
actually think they will both produce the same results, but the
condition in the unassigned_bugs generator is clearer here.

[Lee Bieber (kalebral-deactivatedaccount)]

Thanks for the script, I tried running it, but have not seen a different when I query for unassigned bugs.

[Gavin Panella (allenap)]

Lee, you're right. I've attached an updated script that seems to do the right thing.

[Lee Bieber (kalebral-deactivatedaccount)]

I tried running the latest script but am still seeing a number of bugs in the results which have assignee's.

[Gavin Panella (allenap)]

I've re-run the script and I see two confusing bugs:

- Bug 517384, where there's a bug task for Dexter and Elliot. The
  Dexter task is assigned, but closed, and the Elliot task is
  unassigned, but open.

- Bug 588251, where there's an unassigned and open Elliot task, and
  two other non-Drizzle tasks, one of which is assigned and the other
  which is a bug watch.

I think both of those are correct identified though, by which I mean
that the script has been written to find them, even if it's not very
obvious why.

If you can point me to a specific bug that you don't want to appear in
the search results (and paste a screenshot of the bug task table so I
can see the state of the bug at a specific point in time) then I might
be able to help you modify the script's behaviour to match your
expectations.

[Lee Bieber (kalebral-deactivatedaccount)]

I'm trying to get the proper results when querying for unassigned bugs. Of the 37 bugs that are in the results, the following 10 should not be as they have someone assigned to them

https://bugs.launchpad.net/drizzle/+bug/628398
https://bugs.launchpad.net/drizzle/+bug/628860
https://bugs.launchpad.net/drizzle/+bug/628397
https://bugs.launchpad.net/drizzle/+bug/632755
https://bugs.launchpad.net/drizzle/+bug/648760
https://bugs.launchpad.net/drizzle/+bug/607946
https://bugs.launchpad.net/drizzle/+bug/617056
https://bugs.launchpad.net/drizzle/+bug/628397
https://bugs.launchpad.net/drizzle/+bug/654905
https://bugs.launchpad.net/drizzle/+bug/655805

Would you clarify what you mean by a screenshot of the bug's task table, I thought you should be able to view these bugs and any details about them.

[Gavin Panella (allenap)]

In case the bug was modified after you mentioned it in the report it
would help to have a screenshot of the task table for reference. It's
not essential because assignee changes are recorded in the activity
log, it would just be a convenience. I'll take a look at those bugs
you've listed now.

[Gavin Panella (allenap)]

None of the bugs you have listed are found when I run the v3 version
of the find-unassigned-tasks.py script. Can you check you're running
that same version, unaltered?

[Lee Bieber (kalebral-deactivatedaccount)]

Attaching a screen shot

[Lee Bieber (kalebral-deactivatedaccount)]

Yes, I tried again with version of the script but still am not getting correct results.

[Lee Bieber (kalebral-deactivatedaccount)]

that should be "tried again with version 3 of the script".....

[Gavin Panella (allenap)]

How bizarre. I cannot replicate that :-/

Can anyone else subscribed to this bug replicate the problem? You can
find out by downloading the v3 version of the script (see comment #4)
then running the following:

  $ python -i find-unassigned-tasks.py
  >>> [url for url in unassigned_bug_urls if '628397' in url]
  []

Thank you.