Open
Bug 1352571
Opened 7 years ago
Updated 1 year ago
Support using user mentions in comments to tag people for needinfo
Categories
(bugzilla.mozilla.org :: Extensions, enhancement)
Tracking
()
NEW
People
(Reporter: emceeaich, Unassigned)
References
(Depends on 2 open bugs, Blocks 1 open bug)
Details
(Keywords: bmo-ux)
+++ This bug was initially created as a clone of Bug #634947 +++ Following twitter's '@username' convention for mentions, GitHub uses '@username' for mentions which users get emailed on. We could do the same for needinfo-ing users. User could be mentioned by: * +user@example.org, GSuite style * @user@example.org, Twitter/Github/Mastodon style * :nickname, if user mentioned has a `:nickname` reference in their 'realname' field I thought we had a BMO bug for this but could not find it.
Reporter | ||
Comment 1•7 years ago
|
||
Probably should be blocked on private bugs, since a private bug may be in reference to an action on a bmo user account (suspension/ban/etc.)
Reporter | ||
Comment 2•7 years ago
|
||
Doesn't need to be backfilled on existing bugs.
Comment 3•7 years ago
|
||
I swear I filed a bug for this feature request (automatically setting needinfo or some other flag when there is a user mention in the form of a question). But, I searched and couldn't find the bug. I also couldn't find a mailing list conversation. So I guess it was either an IRC or IRL conversation with some subset of {mcote, glob, dylan, etc} and that's how I ended up being CCd on bug 634947. FWIW, I think user mentions + notifications is the single biggest feature I wish BMO had. It is a subset of a larger feature of "help me find the bugs I need to look at."
Reporter | ||
Comment 4•6 years ago
|
||
:kohei, would you estimate this work? I agree that this is a feature we should have.
Flags: needinfo?(kohei.yoshino)
Comment 5•6 years ago
|
||
I also want to see this, but Bugzilla actually doesn't have usernames like GitHub, Twitter, etc. Adding :nickname to the real name field is just a local practice on BMO. I think Bug 218917 needs to be solved first so the feature will be usable in the upstream as well.
Flags: needinfo?(kohei.yoshino)
Reporter | ||
Comment 7•6 years ago
|
||
Could we do it with the +bugmail@foo.bar convention like Google?
Flags: needinfo?(kohei.yoshino)
Comment 8•6 years ago
|
||
It's an option but feels weird to me. No one uses Google+ any more, while most people are familiar with @username mentions on GitHub and Twitter. Perhaps we could implement prototype code using :username lookups on BMO first :)
Flags: needinfo?(kohei.yoshino)
Comment 9•6 years ago
|
||
FWIW I've seen systems support @<real name>, e.g. CASA (our legal/finance-review tool).
Comment 10•6 years ago
|
||
@username is pretty ubiquitous (GitHub, Bitbucket, GitLab, and Twitter). It is 1 character, so easy to type. A single sigil on the left side makes it easier to implement autocomplete. I think we should go with the common solution rather than create more fragmentation between our tools and the rest of the world.
Comment 11•6 years ago
|
||
As mentioned in Bug 1474153, colon could be used for emoji input. We should have the same behaviour as GitHub not to confuse users. * @username to notify that person (probably needinfo on Bugzilla) * :emoji: to input common emoji https://blog.github.com/2011-03-23-mention-somebody-they-re-notified/
Comment 12•6 years ago
|
||
Note the new /rest/user/suggest API (on bugzilla-dev) will take a match-string beginning with @. e.g. /rest/user/suggest?match=@dkl
Comment 13•6 years ago
|
||
thumbs-up |
It'd be good to encourage people to use nicknames, as having a nickname set makes the migration path away from email as user identifier more straight-foreword.
Comment 14•6 years ago
|
||
I guess the Markdown work needs to be done first.
Depends on: bmo-markdown-initial-release
Blocks: bmo-markdown
Updated•5 years ago
|
Updated•5 years ago
|
No longer blocks: bmo-markdown
Updated•5 years ago
|
Component: Extensions: Needinfo → Extensions
Comment hidden (spam) |
You need to log in
before you can comment on or make changes to this bug.
Description
•