Bug id custom fields should be clickable in bug list

RESOLVED FIXED in Bugzilla 5.0

Status

()

Bugzilla
Query/Bug List
--
enhancement
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: Jens Bannmann, Assigned: Simon Green)

Tracking

4.2.4
Bugzilla 5.0
Bug Flags:
approval +
approval4.4 -

Details

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
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

5 years ago
Severity: normal → enhancement
(Assignee)

Comment 1

5 years ago
Created attachment 706859 [details] [diff] [review]
v1 patch
Assignee: query-and-buglist → hugo.seabrook
Status: NEW → ASSIGNED
Attachment #706859 - Flags: review?
Hugo, you forgot to give a reviewer for this patch :)!
(Assignee)

Comment 3

5 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 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

5 years ago
Flags: approval?
Flags: approval4.4?

Comment 5

5 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
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
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.