+subscribedbugs listing should include bugs subscribed explicitly and implicitly (via team, dupes, etc)

I think this is an use case for bug 1331, therefore a dupe. What do you say, Adam?
Thank you for your report.

Maybe, if someone can point me to the right search to say "show me all the bugs that either I'm subscribed to or a team I'm on is subscribed to, or I'm a bug contact for" or whatever, this might be a use for canned searches. That said, I think this is something that should be more discoverable than "you can use it if you can figure out how to search for it", since to most people who are being assigned bugs to fix, there's no practical difference between "a bug assigned to me" and "a bug assigned to a team I'm on". Either way, they need to see it and they need to fix it.

You may see why this is important to me if you go to my +assignedbugs page and realise that clicking individually on each team to see what bugs are assigned *there* gets significantly more irritating as you are on more and more teams (and I've got a fair number of cute little icons next to my name).

Given that you can already do "All bugs assigned to me" (+assignedbugs), "all bugs subscribed to by me" (+subscribedbugs), and the former has a portlet to allow you to view bugs assigned to teams you're on, while the latter will get such a portlet (if I'm reading the response to bug 61428 correctly), it makes more sense to me to combine these two concepts with another link, either in the "assigned/reported/subscribed/package reports" portlet, or in the "bugss assigned to" portlet, allowing me to see "bugs assigned/subscribed to me and all my teams" or whatever.

matsubara, we should keep this bug open because it's a specific use case.

One way to solve this would be to modify the advanced search form to be your-teams-aware (the assigne widget, for example), and maybe add bug contact filter options.

LaserJock, on IRC, also expressed concern about this bug. He's in pain trying to see all the bugs for MOTU Science.

kiko, can we fix this problem in the next week or two?

Is there a way to see all bugs I am subscribed to (forgetting teams for a moment)? it's unclear from the comments here if it is possible or not, and it looked like the answer is "no" to me, and this feature is absolutely necessary when you don't report a bug but you want to follow it and be able to find it again. I can't search for bugs I am subscribed to in the advanced search or am I missing something?

Hi Vincenzo,

https://launchpad.net/people/vincenzo-ml/+subscribedbugs

You can find that link going to:
https://launchpad.net/people/vincenzo-ml
and clicking on "Bugs" in the LHS portlet. By default Launchpad displays bugs you're assigned to, but you can also choose other display options in the upper LHS portlet.
There's a massive UI change underway and it'll hopefully address that.

Thanks for your comments.

@Diogo

It doesn't display bugs that you are subscribed through duplicates (that is, the "Also notified" thingy).

Testcase: I am subscribed to bug X which is marked as duplicate of bug Y. Therefore, I am subscribed through "Also notified" to bug Y. When I list the bugs that I am subscribed to, bug Y does not appear, nor does bug X because it is a duplicate.

Expected behaviour: either bug X or bug Y are shown in the list of bugs I am subscribed to.

this is still an issue in the new launchpad, I totally disagree with renewing non-critical stuff (like graphics) without first closing important bugs like this.

Every time I'm not @ my pc (without my bookmarks) and want to search a bug where I'm suscribed via duplicate I get crazy....

I discovered that if I go into "advanced search" and scroll all the way down and uncheck "Hide duplicate bugs", then at least I'm allowed to see the missing bugs (albeit not which bugs they redirect to).

Could this option be made the default for the time being, until you come up with a fix for this case (if that is not in fact actually deemed to be a good enough permanent fix)? Pretty please?

And/or how about adding a "Status: Duplicate" so that it's at least possible to see the difference between genuine unconfirmed bugs and bugs whose status and severity assignments are in limbo because they're marked as duplicates of another bug? (Should I perhaps file a separate bug about that?)

> how about adding a "Status: Duplicate"

For the record, that's bug #3796.

Can we get any update on this? +subscribedbugs still doesn't show implicitly subscribed bugs. What's the point of being subscribed if it's not shown in +subscribedbugs? The +packagebugs page only helps you so much (i.e. it's good if you're trying to look for a specific package).

This seems to have been there for a while, is it *that* complicated to fix ? If yes, maybe a +notifiedbugs list could help as a workaround, since implicit subscriptions are listed under "also notified" ?

Marking this as triaged / medium; I don't know when it can be slotted into our schedule, however.

+1 for solving this.

I reported a bug, this has been marked as a duplicate. I'm in the list of "subscribed from duplicates" but the bug is not displayed in any of my bug lists and I can't simply find the bug :(