Bug 965011 - Bug references are not displayed correctly when CVE id is in the summary
Bug references are not displayed correctly when CVE id is in the summary
Status: CLOSED DUPLICATE of bug 964362
Product: Bugzilla
Classification: Community
Component: Creating/Changing Bugs (Show other bugs)
Unspecified Unspecified
medium Severity medium (vote)
: ---
: ---
Assigned To: Simon Green
Depends On:
  Show dependency treegraph
Reported: 2013-05-20 05:50 EDT by Petr Matousek
Modified: 2014-10-12 18:50 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-05-20 06:18:04 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Petr Matousek 2013-05-20 05:50:51 EDT
Description of problem:

Comments referencing bugs with CVE id in the summary via "bug xxx" are not displayed correctly. 

Version-Release number of selected component (if applicable):
Current production Red Hat bugzilla version, 4.4.rc2-3.

How reproducible:

Steps to Reproduce:
1. Enter new comment with "bug XXXX", where XXXX is the number of a bug that has CVE-XXXX-XXXX in the summary (for example bug 962812)
2. Display the comment

Actual results:

For example, https://bugzilla.redhat.com/show_bug.cgi?id=962792#c3 :

Affects: fedora-all [CVE-2013-2094 kernel: perf_swevent_enabled array out-of-bound access [fedora-all]"
   href="show_bug.cgi?id=962799">bug 962799]

Expected results:

Affects: fedora-all [bug 962799]

"bug 962799" having a proper href so you can move to the bug via a mouse click
Comment 1 Petr Matousek 2013-05-20 06:06:10 EDT
Please use "edit" functionality to see the correct version of comment #0. I do not know how (if it's even possible) to avoid autolinkification on per comment basis and it breaks the display of comment #0 even more.
Comment 2 Simon Green 2013-05-20 06:18:04 EDT

*** This bug has been marked as a duplicate of bug 964362 ***

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