Closed Bug 115650 Opened 23 years ago Closed 19 years ago

No TITLE attribute on buglinks on process_bug.cgi.

Categories

(Bugzilla :: User Interface, enhancement, P3)

2.15
enhancement

Tracking

()

RESOLVED FIXED
Bugzilla 3.0

People

(Reporter: BesTo, Assigned: spam)

References

(Blocks 1 open bug)

Details

Attachments

(1 file, 2 obsolete files)

When I make changes to a bug and posting them I've see the bugs this bug depends on. It will be fine to have to each bug-link a title to see whats the bug about.
Depends on: 115796
Priority: -- → P3
Summary: no title when posting a bug → No TITLE attribute on buglinks on process_bug.cgi.
Target Milestone: --- → Bugzilla 2.18
This is fixed by the patch on bug 72863, btw. It doesn't use the method requested in bug 115796, however.
Or the summary of the bug could just be displayed after the 'Changes submitted'/'Checking for dependency' etc lines. I changed that in process_bug.cgi with two lines in 2.14, but I see no way of doing it in a sensible way now that it is done with templates.
The User Interface component now belongs to Gerv. Reassigning all UNCONFIRMED and NEW (but not ASSIGNED) bugs currently owned by Myk (the previous component owner) to Gerv.
Assignee: myk → gerv
Reassigning back to Myk. That stuff about Gerv taking over the User Interface component turned out to be short-lived. Please pardon our confusion, and I'm very sorry about the spam.
Assignee: gerv → myk
Enhancements which don't currently have patches on them which are targetted at 2.18 are being retargetted to 2.20 because we're about to freeze for 2.18. Consideration will be taken for moving items back to 2.18 on a case-by-case basis (but is unlikely for enhancements)
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004. Anything flagged enhancement that hasn't already landed is being pushed out. If this bug is otherwise ready to land, we'll handle it on a case-by-case basis, please set the blocking2.20 flag to '?' if you think it qualifies.
Target Milestone: Bugzilla 2.20 → Bugzilla 2.22
The trunk is now frozen to prepare Bugzilla 2.22. Only bug fixes are accepted, no enhancement bugs. As this bug has a pretty low activity (especially from the assignee), it's retargetted to ---. If you want to work on it and you think you can have it fixed for 2.24, please retarget it accordingly (to 2.24).
Target Milestone: Bugzilla 2.22 → ---
QA Contact: mattyt-bugzilla → default-qa
Attached patch patch for tip (obsolete) — Splinter Review
didn't find how it appears so didn't check dupe.. :-P
Attachment #237607 - Flags: review?
Comment on attachment 237607 [details] [diff] [review] patch for tip >Index: template/en/default/bug/process/midair.html.tmpl >- <a href="show_bug.cgi?id=[% bug_id %]">Throw away my changes, >- and revisit [% terms.bug %] [%+ bug_id %]</a> >+ [% "Throw away my changes, and revisit $terms.bug $bug_id" FILTER bug_link(bug_id) %]</a> Nit: not sure the whole sentence should be linkified. The reason for r- is that this patch doesn't pass test 008filter.t.
Attachment #237607 - Flags: review? → review-
Attached patch patch for tip v2 (obsolete) — Splinter Review
take #9
Attachment #237607 - Attachment is obsolete: true
Attachment #239113 - Flags: review?
Assignee: myk → bmo2007
Blocks: 115796
No longer depends on: 115796
Comment on attachment 239113 [details] [diff] [review] patch for tip v2 >Index: template/en/default/bug/process/confirm-duplicate.html.tmpl >+ <b>Adding the reporter to the CC list of >+ [% "$terms.bug $original_bug_id" >+ FILTER bug_link(original_bug_id) FILTER none %] > [% IF cclist_accessible %] > will immediately > [% ELSE %] > might, in the future, > [% END %] >- allow him/her access to view this [% terms.bug %].</b> >+ allow him/her access to view >+ [% "$terms.bug $duplicate_bug_id" >+ FILTER bug_link(duplicate_bug_id) FILTER none %].</b> > Do you wish to do this? You already linkify the bug # at the beginning of this sentence; there is no need to change "view this bug" as the sentence is explicit enough and already contains a link to the oringinal bug. Moreover, your change is incorrect as it should point to the original bug anyway, not the dupe. Your patch has bitrotten. Else it looks good, but I couldn't test it.
Attachment #239113 - Flags: review? → review-
Attached patch v3Splinter Review
isnt sure what he meant
Attachment #239113 - Attachment is obsolete: true
Attachment #245533 - Flags: review?
Comment on attachment 245533 [details] [diff] [review] v3 >Index: template/en/default/bug/process/midair.html.tmpl >- <a href="show_bug.cgi?id=[% bug_id %]">Throw away my changes, >- and revisit [% terms.bug %] [%+ bug_id %]</a> >+ [% "Throw away my changes, and revisit $terms.bug $bug_id" >+ FILTER bug_link(bug_id) FILTER none %] Maybe shouldn't we link the whole sentence, but only "revisit bug ###". This could be fixed on checkin. r=LpSolit
Attachment #245533 - Flags: review? → review+
just on time for 3.0.
Status: NEW → ASSIGNED
Flags: approval?
Target Milestone: --- → Bugzilla 3.0
Flags: approval? → approval+
Checking in template/en/default/filterexceptions.pl; /cvsroot/mozilla/webtools/bugzilla/template/en/default/filterexceptions.pl,v <-- filterexceptions.pl new revision: 1.90; previous revision: 1.89 done Checking in template/en/default/bug/process/confirm-duplicate.html.tmpl; /cvsroot/mozilla/webtools/bugzilla/template/en/default/bug/process/confirm-duplicate.html.tmpl,v <-- confirm-duplicate.html.tmpl new revision: 1.11; previous revision: 1.10 done Checking in template/en/default/bug/process/midair.html.tmpl; /cvsroot/mozilla/webtools/bugzilla/template/en/default/bug/process/midair.html.tmpl,v <-- midair.html.tmpl new revision: 1.19; previous revision: 1.18 done
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: