Easier bugtracker registration workflow.

[Matthew Paul Thomas]

While adding a bug watch, if the bugtracker is not registered in Launchpad, we should offer a simply confirmation button to register it, instead of presenting a link to the +newbugtracker registration form.

Notice that the current workflow is much better than what was originally reported.

[Diogo Matsubara (matsubara)]

We should also make it easier to add a new bugtracker in the +upstreamtask page,

[Diogo Matsubara (matsubara)]

And the +distrotask page too.

[Diogo Matsubara (matsubara)]

Hi Matthew,

we don't have the +addwatch page anymore and the pages (+distrotask and +upstreamtask) where you can add a watch now displays an error message pointing you to +newbugtracker if you enter an URL of a bug tracker that's not registered in Launchpad. Can this bug be closed?

[Ian Jackson (ijackson)]

Diogo Matsubara writes ("[Bug 4592] Re: Add Watch page (+addwatch) should make it easy to add a new bugtracker"):
> we don't have the +addwatch page anymore and the pages (+distrotask and
> +upstreamtask) where you can add a watch now displays an error message
> pointing you to +newbugtracker if you enter an URL of a bug tracker
> that's not registered in Launchpad. Can this bug be closed?

Does LP now reliably automatically recognise every remote bug tracker
it can cope with ? I tried
  https://launchpad.net/products/malone/+bug/4592/+upstreamtask
and filling in
  autopkgtest (a product of mine just to fill something in)
  http://www.chiark.greenend.org.uk/ (a random URL)
and I get just an error message:
  Launchpad doesn't know what kind of bug tracker this URL is pointing
  at.

I'm afraid I don't have the workflow need to add a tracker right now ...

Ian.

[Diogo Matsubara (matsubara)]

On Tue, Oct 24, 2006 at 06:37:25PM -0000, Ian Jackson wrote:
> Diogo Matsubara writes ("[Bug 4592] Re: Add Watch page (+addwatch) should make it easy to add a new bugtracker"):
> > we don't have the +addwatch page anymore and the pages (+distrotask and
> > +upstreamtask) where you can add a watch now displays an error message
> > pointing you to +newbugtracker if you enter an URL of a bug tracker
> > that's not registered in Launchpad. Can this bug be closed?
>
> Does LP now reliably automatically recognise every remote bug tracker
> it can cope with ? I tried

Yes, the ones it can cope with: Bugzilla, Debbugs, Roundup, Sourceforge and
Trac.
If you enter an URL like:
http://bugzilla.mozilla.com.br/show_bug.cgi?id=613
You'll see a message like:

"The bug tracker at http://bugzilla.mozilla.com.br/ isn't registered in
Launchpad. You need to __register it__ before you can link any bugs to it."

where "register it" is a link to +newbugtracker.

> https://launchpad.net/products/malone/+bug/4592/+upstreamtask
> and filling in
> autopkgtest (a product of mine just to fill something in)
> http://www.chiark.greenend.org.uk/ (a random URL)
> and I get just an error message:
> Launchpad doesn't know what kind of bug tracker this URL is pointing
> at.

Perhaps the message should say something like:

"Launchpad doesn't yet support the kind of bug tracker this URL is pointing
at. Please __file a bug__ requesting support for this BT."

What do you think?
--
Diogo M. Matsubara

[Matthew Paul Thomas (mpt)]

If the bug tracker is of a known type, I think registering it shouldn't require any more effort than entering the URL of the bug report. That would require several changes, I guess, including removing the unnecessary "Name", "Title", and "Summary" fields from bugtracker records. Perhaps this bug report isn't the best place to plan that.

[Ian Jackson (ijackson)]

Diogo Matsubara writes ("Re: [Bug 4592] Re: Add Watch page (+addwatch) should make it easy to add a new bugtracker"):
> "The bug tracker at http://bugzilla.mozilla.com.br/ isn't registered in
> Launchpad. You need to __register it__ before you can link any bugs to it."
>
> where "register it" is a link to +newbugtracker.

Ah, right, that's sensible. Yes, I think I agree that you should
close the bug now.

> Perhaps the message should say something like:
>
> "Launchpad doesn't yet support the kind of bug tracker this URL is pointing
> at. Please __file a bug__ requesting support for this BT."
>
> What do you think?

That wouldn't be unreasonable but I don't think the current behaviour
is unreasonable either.

Thanks,
Ian.

[Diogo Matsubara (matsubara)]

Making the bug tracker registration easier depends on bugs 120142, 120147, 120150

[Björn Tillenius (bjornt)]

It's important to make it easier linking to upstream bugs.

[Eleanor Berger (intellectronica)]

Salgado, I'm re-assigning to you since I think you've got a fix in review.

[Guilherme Salgado (salgado)]

landed on mainline r4811

[Daniel Hahler (blueyed)]

I don't see an improvement with build 4826:
I can not link an upstream bug (https://savannah.nongnu.org/bugs/index.php?21052) easily on https://bugs.edge.launchpad.net/ubuntu/+source/libgksu/+bug/133639/+choose-affected-product

Isn't this bug also about this?

[Guilherme Salgado (salgado)]

On Sat, Sep 15, 2007 at 02:34:26AM -0000, dAniel hAhler wrote:
> I don't see an improvement with build 4826:
> I can not link an upstream bug (https://savannah.nongnu.org/bugs/index.php?21052) easily on https://bugs.edge.launchpad.net/ubuntu/+source/libgksu/+bug/133639/+choose-affected-product
>
> Isn't this bug also about this?
>

No, that is bug 45386.