Bug 974621

Summary:	Generalize "Ubuntu Launchpad" external tracker to just "Launchpad" (incl. URLs change)
Product:	[Community] Bugzilla	Reporter:	Jan Pokorný [poki] <jpokorny>
Component:	Bugzilla General	Assignee:	Simon Green <sgreen>
Status:	CLOSED CURRENTRELEASE	QA Contact:	tools-bugs <tools-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.4	CC:	ebaak, mcepl, rjoost
Target Milestone:	4.4
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	4.4.0005	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	237747	Environment:
Last Closed:	2013-07-31 01:32:25 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	237747
Bug Blocks:

Description Jan Pokorný [poki] 2013-06-14 16:26:32 UTC

This is a follow up of historical [bug 237747].

I have no idea how Launchpad (LP) was structured back then, but nowadays
Launchpad is the place for various (upstream) projects, Ubuntu being
just one of them.  As I think it is useful to link RHBZ bugs to upstream
ones, so to make it easier for LP ones in particular, I suggest
these changes:

"Add External Bug: Tracker" dropdown menu:

- https://bugs.launchpad.net/ubuntu
+ https://bugs.launchpad.net/bugs

- Ubuntu Launchpad
+ Launchpad

(or "Launchpad (Ubuntu and other projects)" if we want to ease referring
to Ubuntu side)

Actually added Launchpad tracker

- https://bugs.launchpad.net/ubuntu/+bug/<id>
+ https://bugs.launchpad.net/bugs/<id>


Note that the current state allows to link LP bugs for other projects
as well because IDs are unique globally per LP and "/ubuntu/+bug/<id>"
URL will get redirected to "/<respective-project>/+bug/<id>" when
appropriate, _but_ the current labelling is counter-intuitive
(e.g., I rather used a comment to link Zope bug: [bug 878961 comment 4]).

Comment 4 Simon Green 2013-07-31 01:32:25 UTC

This change is now live. If there are any issues, do not reopen this bug. Instead, you should create a new bug and reference this bug.

  -- simon