[#JRA-3777] Add Bugzilla portlet

JIRA

Add Bugzilla portlet

Created: 17/May/04 10:33 PM Updated: 20/Jul/04 02:38 AM

Component/s:

Portlets

Affects Version/s:

None

Fix Version/s:

3.0 Pro Preview

Time Tracking:

Not Specified

File Attachments:

bugzillaportlet.diff (9 kB)

Issue Links:

Reference

This issue is related to:

~~JRA-3779~~ Convert bugzilla text links to JIRA links during import

Participants:	Jeff Turner [Atlassian] and Kenny MacLeod
Since last comment:	4 years, 14 weeks, 1 day ago
Resolution Date:	20/Jul/04 02:38 AM
Labels:

Description

« Hide

The Bugzilla portlet is useful for JIRA installations whose original data came from Bugzilla, and whose users want to search for an issue by its old Bugzilla ID. They can enter the ID into the portlet text field, and will be taken to the JIRA issue. If no JIRA issue is found, they are redirected to the Bugzilla issue (eg. the bug was in a project that wasn't imported).

The bugzilla portlet is visible at http://issues.apache.org/jira/

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Jeff Turner [Atlassian] added a comment - 20/May/04 07:10 PM

Attached is a patch against 2.6.1 CVS for the bugzilla portlet. It won't apply cleanly because in the .war/webapp distro the .properties files are in a zip, but if the .properties files are manually patched it can be applied with 'patch -p1 < bugzillaportlet.diff'.

[ Permlink | « Hide ]

Kenny MacLeod added a comment - 21/May/04 04:34 AM

Will this work retrospectively? i.e. will it work on databases which
have already been imported from bugzilla, or will it require a fresh import?

[ Permlink | « Hide ]

Jeff Turner [Atlassian] added a comment - 23/May/04 05:36 PM

It will work retrospectively (it uses the first ChangeLog item that the Bugzilla importer has always added to imported issues).