The discussion revolves around group titles and their functionality in Discourse, particularly how they interact with badges. NomNuggetNom notes that groups lack a feature to automatically assign titles like badges do, and codinghorror confirms the group title setting is enabled but may not work as intended due to refactoring. sam explains that only badges currently allow selectable titles, but a recent fix commit enables group titles to be selectable and resolves UI issues. sam also clarifies that a default group title can be set, but it only applies if members don’t already have a title (e.g., from a badge). erlend_sh adds that users may not get automatic titles due to conflicts between old badge-based titles and new group-based ones. Mittineague shares a real-world example of users valuing their custom titles from legacy systems. Heather_Dudley asks if removing a user from a group removes their title, and sam isn’t certain but suggests it might.
It was always intended to, but I am not sure if it survived refactoring.. I believe @sam was the last person to work on this area, but that was a while ago.
When SitePoint migrated from vB many members had existing custom titles.
One such member asked about titles at Discourse.
When explained that he had a badge that he could use, but that if he tried it his existing custom title might not remain as an option should he want to revert to it (though if he petitioned Staff I’m sure one of them would have changed it for him) he in no way wanted to risk it.
Most of my users did not get their title automatically applied. I’m 99% sure it’s due to user-error because I granted them this new group-based title while most of them still had the old badge-based title, therefore the override did not kick in.
To solve this, I simply
unchecked “Automatically set as primary group” and removed “Contributor” as default title for good measure
Saved.
Reverted my changes in #1
Saved again.
Titles are now appear to be appropriately assigned to all group members.