status_upstream=hide_upstream seems to hide bugs with 'invalid' upstream status

Bug #291968 reported by Chris Cheney
0
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

I have to manage a lot of bugs with openoffice.org in Ubuntu and have noticed that it appears that if a bug has any kind of upstream status at all that hide_upstream hides it. Even if that upstream status is invalid. Also, there is no way to delete an upstream task from a bug.

So with that in mind I can't see bugs if I do a search like this:

https://bugs.edge.launchpad.net/ubuntu/+source/openoffice.org/+bugs?orderby=-datecreated&field.status%3Alist=TRIAGED&field.status_upstream=hide_upstream

This is a MAJOR usability issue to me.

Revision history for this message
Chris Cheney (ccheney) wrote :

Really I would rather this be fixed by allowing the deletion of tasks as long as there is one left on the bug, otherwise it would go into limbo(?). However, just letting hide_upstream not hide invalid upstream status bug would help a lot.

Revision history for this message
Diogo Matsubara (matsubara) wrote :

Deleting a bugtask is bug 1342

Revision history for this message
Chris Cheney (ccheney) wrote :

Diogo,

Well this is still a bug even though it could be possibly worked around if bug 1342 was ever actually fixed. An upstream status of invalid means that upstream does not consider the bug to be an upstream bug which means hide_upstream should not hide the bug in that state. Currently a bug marked invalid upstream has resolved_upstream status, which while strictly true isn't really useful in LP, it effectively means we either have to fix the bug ourselves or somehow convince upstream to fix it, in either case its not really resolved.

Chris

Chris Cheney (ccheney)
Changed in malone:
status: New → Confirmed
Revision history for this message
Chris Cheney (ccheney) wrote :

Actually I was wrong before a bug that has an upstream task that is marked invalid does not show up in searches for bugs marked resolved_upstream or at least not always, perhaps it only shows up in resolved_upstream if the bugs is actually linked instead of just manually tracked.

Here is a case of a bug that does not show up in either hide_upstream or resolved_upstream... one of the 'hidden' bugs essentially which is forcing me to use launchpad api to find the bugs.

Bug which has neither state:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/89005

hide_upstream:
https://bugs.edge.launchpad.net/ubuntu/+source/openoffice.org/+bugs?orderby=-datecreated&field.status%3Alist=TRIAGED&field.status_upstream=hide_upstream

resolved_upstream:
https://bugs.edge.launchpad.net/ubuntu/+source/openoffice.org/+bugs?orderby=-datecreated&field.status_upstream=resolved_upstream

Revision history for this message
Chris Cheney (ccheney) wrote :

So I dug a bit more today along with using launchpadlib to pull out the bug that was effectively hidden.

It appears the web interface does this:

If a bug is upstream it hides it with hide_upstream
If a bug is upstream but not have a bug watch then Invalid status is not considered for resolved_upstream.
If a bug is upstream and has a bug watch then even Invalid status is considered resolved_upstream.

I think probably it would be best to have bugs whether bug watched or not that are Invalid upstream to be not hidden by hide_upstream. Or at the very least treat them both the same way, whichever way you want to treat them.

Using launchpadlib I had to do this to get the equivalent information:

for pkgbug in package.searchTasks(status=['Triaged']):
  for task in pkgbug.bug.bug_tasks:
    if task.target.resource_type_link.split('#')[1] == 'project':
      if task.status == 'Invalid':
        if task.bug_watch is None:
          print task.bug.id, "-", task.bug_target_name

This is a very heavy process, it takes roughly 12m, just to get information that ought to be accessible already.

Revision history for this message
Chris Cheney (ccheney) wrote :

I posted this to my blog so that other bug triagers can be aware of the issue.

http://chrischeney.wordpress.com/2009/03/22/how-to-view-triaged-bugs-that-have-invalid-upstream-tasks/

While composing the blog entry I realized there are really two issues here.

1. external bug trackers invalid status appears to get mapped to something that causes it to show up as resolved_upstream

2. hide_upstream should not hide bugs with upstream tasks that are invalid, regardless of if it is a bugwatch (ie external to launchpad) or not.

Curtis Hovey (sinzui)
Changed in launchpad:
status: Confirmed → Triaged
importance: Undecided → Low
tags: added: bugwatch
William Grant (wgrant)
tags: added: bug-search
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.