Bug 831248 – Unable to link to non-Ubuntu launchpad bugs

Bug 831248 - Unable to link to non-Ubuntu launchpad bugs

Summary:	Unable to link to non-Ubuntu launchpad bugs

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Bugzilla
Classification:	Community
Component:	Bugzilla General (Show other bugs)
Sub Component:
Version:	4.2
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified (vote)
Target Milestone:	---
Target Release:	---
Assigned To:	PnT DevOps Devs
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2012-06-12 10:53 EDT by Russell Bryant
Modified:	2013-06-23 21:46 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2012-06-12 10:56:11 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Russell Bryant 2012-06-12 10:53:46 EDT

Description of problem:

It is currently not possible to add a bug that is on Launchpad, but not Ubuntu, as an External Tracker.  If you select "Ubuntu Launchpad", it generates a URL with "ubuntu" as the project in the URL.  I work on OpenStack (openstack.org), so I have an interest in being able to add external trackers to the following launchpad projects:

nova, glance, keystone, swift, openstack-common, cinder, quantum, horizon

A possible short term solution would be to add entries to the drop down for "OpenStack Nova Launchpad", "OpenStack Glance Launchpad", etc.  Longer term I think it would be useful to add a generic Launchpad entry that lets you enter both a project and a bug number.

Thanks!

Comment 1 Russell Bryant 2012-06-12 10:56:11 EDT

Nevermind.  I just discovered that even though the link says Ubuntu, it gets properly redirected to the right project.  What is there now works.  Thanks.

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