I don’t think Roles are the are the cause of this problem. But you are under a misimpression that needs to be corrected. Correcting it later may let the problem grow too imposing.
Roles often surprise starting users… but only when they start causing problems. They aren’t even aware of Roles before that.
- they don’t realize Roles are required , &
- Gramps is so automated in creating Roles (based on context) in the normal sequences of adding records, that the Role feature goes unnoticed… until there is a Role that is wrong.
To clarify, if a default Role type can be determined when created by context, then it will be.
As examples: adding a NEW Event (with the '+’ icon) uses the Context of the Editor. Within the context of the Family Editor, defaults the Role to Family (with implied Roles of Bride & Groom). Within the Person Editor, defaults the Role to Primary.
However, without that context (as when in the Event view) adding a NEW Event has an UNKNOWN role.
And sharing an Event (whether by drag’n’drop, the Share button/menu item, or clipboard) does not provide any context or the context is ambiguous. So the Role would be set to UNKNOWN there too.
I got bitten by this in 2 spots before learning about roles:
- sharing Birth Events for twins & triplets.
- re-cycling Events that were made redundant by a Person Merge
The most blatant Role problem is when no Birth (and/or Death) appears in the on-screen summaries for a person even though there is a corresponding Event in the Person Editor. (Such summaries might be for the age at Event or indicating the lifespan in the Relationship or Chart views.)