1034073 - Fields accepting bug numbers should get some sort of preview UI / autocomplete

Status: RESOLVED DUPLICATE of bug 1539271

(Bugzilla :: User Interface, enhancement)

Description

[James Graham [:jgraham]]

At present it's very easy to typo a bug number in e.g. the "blocks" field, which results in a lot of confusion and bugspam. Having the same type of preview as for other fields, showing the bug title, would help avoid this.

Apparently bztweaks already has something like this.

Comment 1

[Andre Klapper]

(In reply to James Graham [:jgraham] from comment #0)
> Having the same type of preview as for other fields

like which ones?

Comment 2

[James Graham [:jgraham]]

Like the CC list, or the duplicates list when filing a bug, for example. I'm not saying it's *exactly* the same as those cases, just that it's the same kind of UI.

Comment 4

[Dave Miller [:justdave]]

Copying from bug 1058383, because it had implementation ideas:

-----
It would be cool to autocomplete the blocks and depends-on fields and tokenize the field content once autocompleted.  The tokens would have the bug summary for the title attribute (if available) so you could see what bug it was if you moused over it. (I'm imagining the way Postbox and Zimbra both deal with recipients in their email compose windows - Mozillians also does it with your groups).  The autocomplete dropdown would also list bug summaries to help you pick the correct bug.

A really good data source for the initial autocomplete would be the last-visited data since we track that now (see bug 489028).  Grab the 200 most-recently-visited bugs, since you would most likely be setting a block or depends on something you're looked at recently) and populate your matches initially from that list, perhaps also substring matching on the summaries and not just on bug numbers.  Only start looking outside that list when you don't have anymore matches within it and the user typed a number, and the number of bugs that would be matched is under 100 (like all but two digits typed).

The autocomplete list should be ordered in order of most-recently-visited as well, so the more recently you visited it, the closer to the top of the list it is if it matches.
-----

That bug was specifically for blocks and depends, but would equally apply to things like duplicate etc.

Comment 5

[Dave Miller [:justdave]]

Another potential source (perhaps combine the two) is the results from the last query you ran, if that's easily accessible, in case you found a duplicate in a buglist but didn't actually open it.