Bug 974621 - Generalize "Ubuntu Launchpad" external tracker to just "Launchpad" (incl. URLs change)
Summary: Generalize "Ubuntu Launchpad" external tracker to just "Launchpad" (incl. URL...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: 4.4
Hardware: All
OS: Linux
medium
medium
Target Milestone: 4.4
Assignee: Simon Green
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On: 237747
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-14 16:26 UTC by Jan Pokorný [poki]
Modified: 2018-12-09 06:29 UTC (History)
3 users (show)

Fixed In Version: 4.4.0005
Clone Of: 237747
Environment:
Last Closed: 2013-07-31 01:32:25 UTC
Embargoed:


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.