Not obvious that teams can't have their own bug reports

Bug #244558 reported by Matthew Paul Thomas
28
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Low
Curtis Hovey

Bug Description

Occasionally I have seen people on mailing lists and IRC (and Matthew Barker in person) register a team, and then try to report bugs assigned to this team, without first having a relevant project to file the bugs against.

I don't know of an obvious solution to this problem -- it might require several small changes to each of the "People and teams", "Register a new team", and team Bugs pages.

<Laibsch> I can't even file a bug or a question against vcs-imports
<jml> that's because vcs-imports is a team
...
<jml> you can't file a bug against a team
<Laibsch> well, LP suggests it is possible ;-)
<jml> where?
<Laibsch> LP can be pretty confusing there
<Laibsch> https://bugs.launchpad.net/~vcs-imports
<Laibsch> https://answers.launchpad.net/~vcs-imports
<Laibsch> the sheer existence of that page
<jml> Laibsch: I don't find that so confusing. I mean, I wouldn't think I could file a bug on https://bugs.edge.launchpad.net/~r0lf
<Laibsch> well, but the page at least has a meaning
<Laibsch> so, I would say the natural thing is to assume that the page has some meaning
<Laibsch> All I am saying is it can be confusing
<Laibsch> It confused me
<LaserJock> I kind of agree with Laibsch
<LaserJock> though I know you can't
<LaserJock> 1) I'd often like to file bugs against teams
<andrea-bs> how about a message "This page is not to report a bug against this team/person" on the top of the page?
<jml> andrea-bs: maybe
<Laibsch> andrea-bs: why not eliminate that page for teams?
<LaserJock> 2) a team can be subscribed and assigned to bugs, seems logical to be able to file a bug against a team
<jml> andrea-bs: a thing with that style of solution is that there are many things that the page is not :)
<LaserJock> Laibsch: what page?
<Laibsch> https://bugs.launchpad.net/~vcs-imports
<jml> Laibsch: because it's *useful*
<Laibsch> https://answers.launchpad.net/~vcs-imports
<andrea-bs> Laibsch: because it is useful to see which bugs are related to a team/person
<LaserJock> Laibsch: those pages are useful
<Laibsch> OK
<LaserJock> heh
<LaserJock> it's just you can file a bug against a team, but you can subscribe or assigne the team to a bug
<LaserJock> *can't file
<jml> LaserJock: something along the lines of filing bugs against people or teams would be useful
<jml> LaserJock: except probably not actual defect reports
<andrea-bs> jml: mh... maybe giving some buttons to report bugs to the related projects?
...
<LaserJock> it's especially useful if there isn't a related project
...
<LaserJock> hmm, I wonder if people appling for membership in a team could be treated as a bug
<jml> andrea-bs: yeah, I like that idea more.
...
<LaserJock> andrea-bs: how do you know what the related project is?
<andrea-bs> LaserJock: when a team is linked to a project (e.g. is a bug supervisor)
<jml> LaserJock: "most active in" is another way of getting a short list

Related branches

description: updated
Revision history for this message
Curtis Hovey (sinzui) wrote :

I hope this will be addressed in https://blueprints.launchpad.net/launchpad-registry/+spec/project-affiliation which we are discussing now.

Changed in launchpad-registry:
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Curtis Hovey (sinzui) wrote :

This issue is really about the bug tracker and the bug reporting process.

affects: launchpad-registry → malone
Curtis Hovey (sinzui)
tags: added: teams
removed: registry-people
Revision history for this message
Martin Pool (mbp) wrote :

Beyond the actually current title "Not obvious that teams can't have their own bug reports", it is often not obvious that a particular page is about a team.

Revision history for this message
Curtis Hovey (sinzui) wrote :

Looking at the ~launchpad team bug page <https://bugs.launchpad.net/~launchpad>, I see several things wrongly implied. I believe much, maybe all are reported as bugs, but I do not think there is a comprehensive list. This is was frustrates me:
1. The page title is bogus. it does not mention the team. This is because several bug view go out of their way to break the page title rules. /me weeps.
   related bugs : Canonical Launchpad Engineering

2. Where the breadcrumbs? No doubt they were lost by the same effort to break the page title.
   Canonical Launchpad Engineering > related bugs

3. The heading is not wrong, but since teams and projects share namespaces, the page might say
   Bugs related to the Canonical Launchpad Engineering team

4. 3 of the 7 navigation links in the side bar are impossible. I cannot log in as a team to report a bug, comment on a bug, or be affected by a bug. The valid links are
   All related bugs
   Assigned bugs
   Subscribed bugs
   Subscribed packages

5. I cannot see any links to the projects that this team is affiliated with that use Lp bugs. A project will tell me if the Ubuntu package also tracks bugs. There is no hint as to which projects the team has extra permission to work bugs. I would love to see a list of project on my own bug page to remind me of my responsibilities as maintainer, driver, supervisor, and security contact.

6. The default bug data (columns) is wrong. My choices for projects will not be the same as people and teams. Not ever. I need to see the projects which is something I rarely need to see for projects.

Revision history for this message
Robert Collins (lifeless) wrote :

Page title is bug 516485

Revision history for this message
Matthew Paul Thomas (mpt) wrote :

That's #1, and I've reported #3 as bug 928234. I think it would be quite possible to fix all six of those problems without actually fixing this bug. But a sufficiently thoughtful fix for #5 might fix this bug too. Maybe all that would be needed is intro text of the form "The {name} team is involved with bug reports on these projects:"

Curtis Hovey (sinzui)
Changed in launchpad:
assignee: nobody → Curtis Hovey (sinzui)
status: Triaged → In Progress
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
Changed in launchpad:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
tags: added: qa-ok
removed: qa-needstesting
William Grant (wgrant)
Changed in launchpad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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