1217538 - Prioritize frequently used contacts in user fields

Status: NEW

(Bugzilla :: Creating/Changing Bugs, enhancement)

Description

[Tiffanie Shakespeare [:tif]]

STR:

1. In an already open bug, find the cc field to add a new person.
2. Start typing and observe the search result list

Rather than prioritizing people I frequently add to bugs, I instead have to navigate through the whole list each time.

For example, we have many Patryk's, but I only ever add one to bugs. Rather than his listing be shown first, I have to either continue on to typing his last name or scroll through the list to find the correct person.

Comment 1

[Tiffanie Shakespeare [:tif]]

It appears glob was the incorrect contact. Trying again. Thanks!

Comment 2

[:glob ✱]

(In reply to Tiffanie Shakespeare [:tif] UX from comment #1)
> It appears glob was the incorrect contact. Trying again. Thanks!

i don't need to be cc'd as i'm watching the component :)

Comment 3

[Dylan Hardison [:dylan] (he/him)]

There are a lot of Dylans as well. I think this would be a sensible thing to do.

- store the relationship between the two users (user-a needinfo user-b, user-a cc user-b)
- when performing auto-completion for user-a, add a weight for any user-b's in that same type of field (needinfo or cc).

Comment 4

[Frédéric Buclin]

(In reply to Dylan William Hardison [:dylan] from comment #3)
> - store the relationship between the two users (user-a needinfo user-b,
> user-a cc user-b)
> - when performing auto-completion for user-a, add a weight for any user-b's
> in that same type of field (needinfo or cc).

The type of field is overkill. The probability to have distinct "dylan" or "patryk" or "lambda user" for different user fields is small and not worth the complexity. And for the rare cases where this happens, the generated list would be so small that it doesn't harm to have them merged.

Comment 5

[Tiffanie Shakespeare [:tif]]

I agree with Frédéric, I don't think we need a prioritized list for each field as I think generally the cc and NI lists are going to be very similar.

Sorry if my wording was confusing - I was having trouble articulating my idea as I didn't know the generic phrase "user field" for those items :)