Closed
Bug 833752
Opened 11 years ago
Closed 11 years ago
Bug id custom fields should be clickable in bug list
Categories
(Bugzilla :: Query/Bug List, enhancement)
Tracking
()
RESOLVED
FIXED
Bugzilla 5.0
People
(Reporter: jens.b, Assigned: mail)
Details
Attachments
(1 file)
799 bytes,
patch
|
dkl
:
review+
|
Details | Diff | Splinter Review |
When a bug list is configured to include a custom "bug ID" field, the value should be a link to the bug. Right now, we have to copy/paste the number into the search box, or open the bug page that displays the custom field as a link.
Updated•11 years ago
|
Severity: normal → enhancement
Assignee | ||
Comment 1•11 years ago
|
||
Assignee: query-and-buglist → hugo.seabrook
Status: NEW → ASSIGNED
Attachment #706859 -
Flags: review?
Comment 2•11 years ago
|
||
Hugo, you forgot to give a reviewer for this patch :)!
Assignee | ||
Comment 3•11 years ago
|
||
(In reply to Sunil Joshi from comment #2) > Hugo, you forgot to give a reviewer for this patch :)! Do I need to do that? I currently have six patches that don't have a reviewer (and three that do), but they seem to be picked up by one of the Mozilla guys eventually (usually Frédéric). How do I know who to give it to? Regards, Hugo
Comment 4•11 years ago
|
||
Comment on attachment 706859 [details] [diff] [review] v1 patch Review of attachment 706859 [details] [diff] [review]: ----------------------------------------------------------------- Looks good and works as expected. r=dkl
Attachment #706859 -
Flags: review? → review+
Assignee | ||
Updated•11 years ago
|
Flags: approval?
Flags: approval4.4?
Comment 5•11 years ago
|
||
Enhancement requests are targetted 5.0 now that we are post 4.4rc1.
Flags: approval?
Flags: approval4.4?
Flags: approval4.4-
Flags: approval+
Target Milestone: --- → Bugzilla 5.0
Comment 6•11 years ago
|
||
Committing to: bzr+ssh://dlawrence%40mozilla.com@bzr.mozilla.org/bugzilla/trunk modified template/en/default/list/table.html.tmpl Committed revision 8567.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•