We should be able to add tags while reporting bugs.

I think this would be a bad idea, both because it would make the form more complicated, and because it would lead to greater use of frivolous tags.

And just to start what will hopefully not be heavy use of comparisons between Launchpad and Google Code Hosting, :-) Google doesn't let you enter labels when entering a bug report even though they use labels for prioritization.

Can you give some examples of how it would be useful to add tags when reporting a bug?

On Mon, Jul 31, 2006 at 04:48:39AM -0000, Matthew Paul Thomas wrote:
> And just to start what will hopefully not be heavy use of comparisons
> between Launchpad and Google Code Hosting, :-) Google doesn't let you
> enter labels when entering a bug report even though they use labels for
> prioritization.

Actually you can. I took some time today playing around with it today.
If you're a project owner or member the form to report issues look a bit
different. (As shown in the attached screenshot.)
flickr.com too let you add tags when uploading photos.

>
> Can you give some examples of how it would be useful to add tags when
> reporting a bug?

When I reported this bug, I previously reported three other bugs that I wanted
to add tags to, and had to follow the workflow:
1. Report the bug;
2. Edit its description to add tags.

Between steps 1 and 2 I had to click around the UI many times and found this
an annoyance. It'd be much easier to accomplish that only on one step.

An useful example of tags are to arbitrarily group bugs of a given category.
For instance, if I'm reporting bugs in the UI, I'd like to add a tag
to it saying that it's UI related, that way our UI expert could find all of
them easily. If I have to go thru lots of clicks to do that I just won't bother,
and we'll lose some extra metadata that users are willing to add to the bug.

Make sense?

--
Diogo M. Matsubara

Note that all the entry boxes below the "Attach a file" link are not visible to people not involved with the project. From the look of the screenshot, you are an administrator of that project.

On Tue, Aug 01, 2006 at 08:40:02AM -0000, James Henstridge wrote:
> Note that all the entry boxes below the "Attach a file" link are not
> visible to people not involved with the project. From the look of the
> screenshot, you are an administrator of that project.

That's why I said: "If you're a project owner or member...".

Perhaps we could make something similar at the +filebug form, displaying the
tag field if the users has any association with the context product or distro.

--
Diogo M. Matsubara

That seems like a reasonable idea.

The problem between steps 1 and 2 is endemic to bug details in general, not just tags in particular.

Tagging issues when reporting them is useful, but maybe this feature should only be offered to project members and owners, since those are the people who do the triaging and assigning as well.

FWIW, my guided filebug branch has a link to a "complicated bug filing form", which, I think, gives us some leeway in crafting it for the power user.

I agree with the idea that we should be able to add tags while filing, but only for (some appropriate group of) expert users, such as project owners. I think these users wouldn't want a guided filing process but rather everything on one page.

Maybe there could be checkboxes for the most commonly used tags?

I think this shouldn't be added for everybody, but just to a restricted group, as the project bug contact.

Anyway, I can't find a good reason to just have this and not have an Assignee, Importance, Milestone, State... field, since then you'll have to edit them too after submitting the bug. Also note that +advanced has tags, as you've already said, but doesn't have those other fields, which are, IMHO, more important (no that tags isn't important, but I use those 4 fields more than the tags).

I'm marking this bug as fixed, since it's already possible to add tags while reporting bugs by using the complicated form. We might combine the two forms, but that's tracked in bug 89146.