Closed
Bug 320918
Opened 20 years ago
Closed 16 years ago
autolinkification should display the bug summary next to its number
Categories
(Bugzilla :: Creating/Changing Bugs, enhancement)
Bugzilla
Creating/Changing Bugs
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: dfc, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051118 Debian/1.4.99+1.5rc3.dfsg-1 Firefox/1.5
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051118 Debian/1.4.99+1.5rc3.dfsg-1 Firefox/1.5
The autolinkification feature should be able to use the summary instead of or in addition to the actual number. A lot of extra clicks could be saved if you knew what the bug was about when you came across bug 123456 Printing the title in addition to the number or instead of the number would cut down on this extra click. At the very least the summary could be a tooltip when you hovered over a link.
Reproducible: Always
Steps to Reproduce:
| Reporter | ||
Comment 1•20 years ago
|
||
@mkanat> dfc: That's actually usually the "title" attribute of the <a>.
Comment 2•20 years ago
|
||
Do you have a specific example of where this is happening? As far as I knew we already did exactly this...
| Reporter | ||
Comment 3•20 years ago
|
||
I just checked and you are correct it does put the title in as the link title. It must have been something screwy with my browser at home.
Can I change this one to be a request that bugzilla print the summary in addtion to or along side the number? It would make printing and scanning the screen easier...
eg
bug 320918
would end up being
"Bug 320918 (autolinkification should use the summary for the link or tooltip)"
Comment 4•20 years ago
|
||
Maybe you fell on a security bug (like bug 123456). In this case, the bug summary is hidden for security reasons.
OS: Linux → All
Hardware: PC → All
Summary: autolinkification should use the summary for the link or tooltip → autolinkification should display the bug summary next to its number
Whiteboard: see comment 3
Comment 6•19 years ago
|
||
I'd prefer this not happen; having automatic text stuck into the middle of a comment tends to break the comment's readability.
In fact, I'd really like an option to not have "[details]" inserted into the comment text after an attachment autolink. In this case, once isn't really a problem, but when a comment containing an autolink is quoted, the auto-text ends up quoted and then repeated by the new autolink, as seen here:
> attachment 1 [details] [diff] [review]
That kind of repetition with bug summaries would get out of hand, I think. At least the "details" link is arguably necessary as it's a different link than the original attachment value, and one that's not readily available (if the attachment is from another bug) either in the current page or by following the attachment link.
Comment 7•16 years ago
|
||
wontfix based on Mike's comment #6.
This won't ever happen for autolinkification in continuous text comments, because it would make any comments with references to bugs like bug 123456 (Autolinikification next to the bug number makes continuous text comments unreadable) or bug 1234567 (Implement option to show summary details on demand for dependency fields) completely unreadable.
In comments, we could only consider auto-adding the summary next to the number IF the user deliberately creates a list of bugs with *one bug on each line*. So we could convert
bug 123456
bug 1234567
into
o _Bug 123456_: Autolinikification next to the bug number makes continuous text
comments unreadable
o _Bug 1234567_: Implement option to show summary details on demand for
dependency fields
Or we could implement an option to show summary details on demand for dependency fields, like this:
Blocks: 123456, 1234567 (_details v_, _edit_)
...where clicking on _details v_ would expand the list like this:
Blocks:
o _Bug 123456_: Autolinikification next to the bug number makes continuous text
comments unreadable
o _Bug 1234567_: Implement option to show summary details on demand for
dependency fields
Where o represents a html-formatted bulleted list.
But all of these proposals probably need new bugs for a clean start.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WONTFIX
Updated•16 years ago
|
Whiteboard: see comment 3
You need to log in
before you can comment on or make changes to this bug.
Description
•