Registering a bug tracker is prohibitively difficult

Similarly, there is no way to link an existing bug tracker to a project.

(of course, we don't make much use of the projext <-> bug tracker linkage at the moment)

Linking an existing bug tracker to a project is bug 2879.

instead of having this message when we click on "upstream" and the bug tracker doesn't exist yet:
"The bug tracker in which the remote bug is found. Choose from the list. You can register additional bug trackers from the Malone home page."

it would be better to have:
"The bug tracker in which the remote bug is found. Choose from the list. You can register additional bug trackers by clicking HERE"

Had yet another rock star asking how to do this this morning (Sidnei da Silva), so I'm confirming this bug. :)

Linking an existing product to a project is bug 1132

I tried to link to an uptream bug for parted today for bug 50959 but had to give up in the end. I did manage to register a tracker for parted after jumping through many hoops but when trying to link to the bug it failed in the end anyway.

For Ubuntu upstreaming bugs is extremely important because we have no other way of addressing the 30 000 open bugs across 20 000 packages. We are not upstreaming as much as we should, and this problem is one reason (another is that we need to educate our volunteer triagers to do more upstreaming, but that's sort of blocked on this problem).

It was very hard to find where to register bug tracker. In the end I found it:
On main page: click bugs
After much searching on that page and asking on irc channel, found that I had to click on the quite hidden link in "including 35613 links to 149 bug trackers" near bottom of that page. (It is not in a menu on the side like things normally are in launchpad and therefore not where users expect to find it). After that it was just clicking on "Register bug tracker" (this time in a menu on the left...)

Maybe add a link to "register new external bug tracker" to the "Change details" page of projects (add it near the list box for selecting external bug tracker).

This can be fixed as follows: On the page where you link to a remote project (by URL, by e-mail address, or no link), you should have an option (i.e. a link) to add a remote bug tracker (under the URL box, I'd imagine) if and only if one is not already linked.

Adding this one link should be pretty simple.

Duplicate #540200 is pretty much exactly about comment #7 above: the instructions already suggest that this should be possible, but I could not find a way to do it!

'https://bugs.launchpad.net/bugs/bugtrackers/auto-debbugs.gnu.org says "You can link a registered project to a registered bug tracker in the project's “Change details” page."

However, on the page https://bugs.launchpad.net/bugs/bugtrackers/auto-debbugs.gnu.org/+edit I cannot see where to add a link to the upstream GNU Emacs project.

There is a project page at https://launchpad.net/emacs which presumably I should be able to add somewhere.'

Bug trackers are shared by projects, so to set emacs to auto-debbugs.gnu.org, visit emacs+edit, choose the bug tracker from the insane list of trackers, and enter emacs' bug tracker id/name in the remote bug tracker field.

The widget for setting the bug tracker has separated the bug tracker field from the remote project field. The list of bug tracker swould be smaller if users could see that they do not need to register a tracker for each project.

I realize now that it says "the _project's_ 'Change details' page" but I cannot find such a page. What I primarily wanted to suggest in bug #540200 was that this text is misleading and should be changed, either to a correct link, or removed altogether if there is no good documented way to link a project to a bug tracker.

> visit emacs+edit

I don't understand this part of the instruction. Could you give a URL perhaps? I tried https://bugs.launchpad.net/emacs+edit and a bunch of other alternatives I could think of (slash instead of plus, try removing "bugs" from the URL), but none of them worked.

Based on comments in bug #2879, I found https://launchpad.net/projects/emacs/+edit but it says "Not allowed here. Sorry, you don't have permission to access this page". What permissions do I need in order to be able to do this? Is this documented somewhere? Should I submit a bug report against Launchpad to get an administrator to add the link from the project to the bug tracker?

Only the project owner/maintain can use Change details. We are planing two kinds of changes to address this situation:
1. Create a single screen to configure bugtracking information and make the links to it clear.
2. Open the permissions ong fields needs by many communities so that anyone can provide missing information and allow users to fix data that the Registry Admins own.

Emancs is owned by the Regisrtry Admins. I make anyone the maintainer of this project if they wish.

I would like to propose to change the ownership of the Emacs upstream project to the ubuntu-elisp Launchpad group, but that's outside the scope of this bug report.

https://lists.launchpad.net/ubuntu-elisp/msg00038.html

Fixed in stable r11051 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/11051>.