A person/team can't control use of their own bug tags

Bug #193585 reported by Matthew Paul Thomas
26
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

Individuals or members of a team may want to use bug tags that cannot be added or removed by anyone else, similar to how a bug's Importance cannot be changed by people outside that project.

For example, the Ubuntu kernel team wants to mark particular bugs as particularly deserving of their attention; this would lead to arguments if anyone else had permission to add or remove the tag too.

Individuals may also want to have their own lists of bugs they'd like to work on when they have time (bug 487272).

One way of implementing this would be for each person and team to have control over any tag starting with their Launchpad ID followed by a particular character that isn't allowed in either Launchpad IDs or tag names. (This character should not be a colon, because that should be reserved for advanced operators as in bug 5594.) For example, members of the Canonical QA team would be able to add or remove tags like "canonical-qa.kernel", "canonical-qa.desktop", "canonical-qa.server", in a bug report without anyone else having permission to add or remove them.

If a person or team changed their Launchpad ID, or was merged into another, all their tags would need to be changed too. And if a person's account was deactivated, or a team ceased to exist, all their tags should be removed, though this would not need to be done synchronously.

This is not the same as bug 159036, which is about having tags that are officially recognized but that can be added or removed by anyone.

description: updated
Revision history for this message
Björn Tillenius (bjornt) wrote : Re: [Bug 193585] [NEW] A project can't control use of its own bug tags

On Wed, Feb 20, 2008 at 05:27:29AM -0000, Matthew Paul Thomas wrote:
> One way of implementing this would be for each project and distribution
> to have control over any tag starting with the ID of that
> project/distribution followed by a dot. For example, members of Ubuntu
> Drivers would be able to add or remove "ubuntu.kernel", "ubuntu.mid",
> "ubuntu.partner", etc tags in a bug report without anyone else having
> permission to add or remove them.

This is not a bad idea. Couldn't we have it on a person and team level
instead? It should solve the same use case, while solving another use
case as well; being able to create bug listings that only I'm interested
in.

Revision history for this message
Matthew Paul Thomas (mpt) wrote : Re: A project can't control use of its own bug tags

Yes, that would be even better.

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

mpt, isn't bug 66842 a dupe of this one?

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

It is not. Bug 66842 is about having Launchpad remember which tags are interesting to you, regardless of who created them. This bug is about having tags that other people/teams cannot use.

Revision history for this message
Omegamormegil (omegamormegil) wrote :

I'd like to use tags to better organize the bugs I'm personally interested in, without creating lots of tag spam for everyone else.

Changed in malone:
status: New → Confirmed
description: updated
Curtis Hovey (sinzui)
Changed in malone:
status: Confirmed → Triaged
importance: Undecided → Low
description: updated
Curtis Hovey (sinzui)
tags: added: teams ubuntu-platform users
Revision history for this message
Bryce Harrington (bryce) wrote :

This came up as a potential escalation by Ubuntu today in one of the UDS sessions, although it was decided not to escalate this until needs are a bit better understood.

More specifically, the need that was stated is for a way for developers to keep track of bugs that they might be interested in fixing some day, but they aren't ready to *commit* to fixing them (which is what assignment seems to imply).

Currently people either a) abuse the assignee tag for this, b) abuse the bug tags by setting personal tags, or c) get abused by trying to do this with bug subscriptions.

Personal bug tags was one solution mentioned by Curtis for addressing this need.

Revision history for this message
Martin Pool (mbp) wrote : Re: [Bug 193585] Re: A person/team can't control use of their own bug tags

Another option they can do today is to mark the bug as affecting them,
and then they can find either all the bugs globally that affect them,
or those within a particular project.

This is arguably abuse too but perhaps of a smaller kind.

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.