2035: document.title (tab name) should include bug number and submitter

keshav*******@gmai***** (Google Code) (Is this you? Claim this profile.)
March 19, 2011 
I'm using Review Board 1.5.4.1

The format for document.title (the field used for the web browser tab name) should be improved. Currently, the tab name is just the review summary (the "title" of the review). But it should be something like this:
  (<submitter userid>) <bug numbers, if any> <review summary>

A format like this would make it easy to:
 - identify a review from the tab name, and
 - identify which bug tabs match which review tabs from the tab names.

The submitter/assignee should probably be omitted from the tab name whenever the submitter matches the logged-in user, as in that case it's probably a waste of space. But including it is very useful for identifying and distinguishing among the reviews of others.

Nice to haves:
  - The format could be configurable, so that a company using RB can set a default review tab format that matches, say, the format used by Bugzilla bug tabs.
  - There could be an option to shorten tab names by, for example, replacing words with common acronyms, eliminating vowels, etc.

Thanks,
Keshav
david
#1 david 
This kind of customization is quite specific to individual sites, and the marginal utility of it is offset by the additional complexity in the UI which it would require to be optional or configurable. I suggest if you want this change, that you make it on your own.
  • +WontFix
#2 keshav*******@gmai***** (Google Code) (Is this you? Claim this profile.) 
If you have 5 tabs open with 5 reviews, and you have to click through all of them just to find a single review, then something is wrong with the tab name. Wouldn't you agree?

Do you not open multiple tabs in your web browser? Don't review summaries usually get truncated when they appear as the tab names? Doesn't that make it harder to know which review is in which tab without clicking on it? Given that Review Board is a browser-based app, isn't the problem of trying to find a review open on your desktop by looking through your web browser tabs pretty universal for RB users (not site-specific)?

You mentioned "the additional complexity in the UI which it would require to be optional or configurable." Are you saying that there are already too many checkboxes under RB User Preferences?

Is it so complex to make it optional? I haven't looked at RB code, so this is just guessing, but isn't implementing this feature like 10 or 20 lines of code? I.e. add a checkbox, add the appropriate localized strings to display in the UI next to the checkbox, make that setting persistent in the DB, and optionally prefix the tab name with submitter and bug number. It sounds like half an hour of work to write and test it... is it actually a more complex picture than I'm imagining?

Thanks,
Keshav