Closed Bug 290288 Opened 21 years ago Closed 19 years ago

There are better HTML titles than "Bug processed"

Categories

(Bugzilla :: User Interface, defect)

2.19.1
defect
Not set
minor

Tracking

()

RESOLVED FIXED
Bugzilla 3.0

People

(Reporter: u20230201, Assigned: LpSolit)

References

Details

Attachments

(1 file)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040906 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040906 After having changed a bug the HTML title is set to "Bug processed". I would like to have the bug number included between those two words at least. Generally I think the HTML title (usually title of windows or tab in the browser) should reflect what's currently being displayed. Adding specific information will help picking the right window from either a list of tabs or windows when changing windows via Alt+Tab or so. I'm sure there are other examples, not just "Bug processed", but you'll get the idea I guess. Reproducible: Always Steps to Reproduce: 1. Apply some change to a bug Actual Results: Windows title is "Bug processed" Expected Results: A smarter type of title
Yes, I definitely agree. :-) Particularly when I have a lot of tabs open, "Bug Processed" is really unhelpful. :-)
Assignee: create-and-change → myk
Severity: enhancement → minor
Component: Creating/Changing Bugs → User Interface
Version: unspecified → 2.19.1
Status: UNCONFIRMED → NEW
Ever confirmed: true
IMO, if the page title changes to "Bug NNN processed" or similar (which sounds like a GOOD idea) then bug 63536 should also be fixed. It is already misleading to have the "wrong" bug shown after submitting, and would be highly misleading to have a page title starting "Bug YYY", but showing bug XXX. (Conversely, some consideration should be given to a "correct" page title for people who do prefer to configure it to go to a different bug after processing....)
If we go to a new bug after processing the last one, whether or not we have a user preference for it yet, the title of the page should be "Bug NNN processed; Bug YYY <summary>", so that users can tell from the title of the page both what bug was processed and what bug is being displayed next.
While we're at it: I've decided to add this enhancement to this enhancement request: After submitting changes ("Changes submitted", "Bug processed") the text "Back To Bug #12345" should be enriched with the summary of that bug. That's maybe more obvious if you keep multiple bugzilla tabs open in your bowser over night. Can you still remember what your last filed bug was about? Me not always. So it would be a significant alternative to having to visit the link taget first. Maybe the weakest solution could be adding a title attribute with the bug's summary to the hyperlink.
Whiteboard: [Good intro bug]
Assignee: myk → ui
Target Milestone: --- → Bugzilla 3.2
Blocks: 365076
Attached patch patch, v1Splinter Review
If a single bug is edited: Bug XXX processed If multiple bugs are edited: Bugs processed
Assignee: ui → LpSolit
Status: NEW → ASSIGNED
Attachment #253942 - Flags: review?(mkanat)
Comment on attachment 253942 [details] [diff] [review] patch, v1 Yeah, I suppose that works. There should be some better way than using the CGI, though.
Attachment #253942 - Flags: review?(mkanat) → review+
Flags: approval+
Whiteboard: [Good intro bug]
Target Milestone: Bugzilla 3.2 → Bugzilla 3.0
Checking in template/en/default/bug/process/header.html.tmpl; /cvsroot/mozilla/webtools/bugzilla/template/en/default/bug/process/header.html.tmpl,v <-- header.html.tmpl new revision: 1.5; previous revision: 1.4 done
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
In reply to comment #7: While making nails with heads, what about something like "%u Bugs processed" for the case of multiple bugs? Is it possible within templates?
(In reply to comment #10) > like "%u Bugs processed" for the case of multiple bugs? Is it possible within > templates? Templates do not have this information available. And I don't consider this information as useful enough to worth the change.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: