Here is my business case to be clearer what will be great to accomplish.
In our company we have 40 branch offices connetcetd to our Discource.
Every branch office have around 8 specific generic roles.
Every branch office have HelpDesk role, InfoDesk Role , Manager Role, Support Role et cetera.
We already have user groups for branches and for roles.
But when I type my post,
I know that there is Manager at BihacBranceOffice but I can’t figure his name.
If I call @Managers group I’ll get 40 members, If I call @BihacBrancOffice ill get 12 members.
An idea is to make user field with generic convention BrnacOfficeRole also another one RoleBrancOffice.
That fields should be pickable in @DopNDownList
That will make more easy to comunicate.
Users can easly call specific roles.
If someone start typing @NameOfBrancOffice it can see all roles there.
Olaso if somoneo writes @roleName it will get list off all specific persons tehre.
I know that Discourse is focused on Human conversation, But from business perspective there is fluctuation in personal.
I can remember that @OneSpecificPersonWhitNameAndSurname is Manager at that Branch Office but business rules is perhaps going to change people and their roles over time, Helpdeskres goes to managers, Managers Cheng theri Brnec Offices ans so one.