~Team bugs page searches only show bugs where the relation is the team rather than any members of the team

[Graham Binns]

If you visit https://bugs.edge.launchpad.net/~ubuntu-foundations you'll see no bugs (at the time of writing; screenshot attached). This is because ubuntu-foundations isn't directly related to any bug as a first-class Person object. However, the members of the team are related to many bugs. The bugs to which a team's members are related should be shown in its related bugs page. This also holds true for +subscribedbugs, +assignedbugs, etc.

[François Marier (fmarier)]

The "reported bug" page is also affected, but in this case it's even more important IMHO because there's no way (as far as I can tell) to change the reporter of a bug to be a team, or to file a bug on behalf of a specific team.

I'd like to be able to quickly see what bugs were filed by Mahara Contributors (https://launchpad.net/~mahara-contributors) like Ruslan (https://bugs.launchpad.net/~ruslan-kabalin) but https://bugs.launchpad.net/~mahara-contributors/+reportedbugs doesn't show the bugs reported by team member.

[Matthew Paul Thomas (mpt)]

Implicit in duplicate bug 396319 is that showing bugs for all team members is useful only if you can see *which* team member is involved in each case.

Therefore, ~team/+assignedbugs should include an "Assignee" column or subheadings, and ~team/+reportedbugs should include a "Reporter" column or subheadings.

For the purpose of this bug, ~team/+subscribedbugs and ~team/+packagebugs probably shouldn't change at all.

[Matthew Paul Thomas (mpt)]

Partial workaround: Add “/+upcomingwork” to the end of the team URL. Ignore that the page repeatedly says “Blueprint”: the items listed are bug reports assigned to various members of the team. Drawback: This works only for bugs with a future milestone, not those with a past milestone or no milestone.