This is a reasonable suggestion for enhancement. But it is being inserted in the wrong feedback area. This discussion is about improving the documentation for the features as they exist today. (That documenting process often spawns issue reports and feature requests.) However, this suggestion should in Ideas and could reference this thread.
I seem to recall related discussion threads and feature requests. Related to different aspects: the handling of the Events with undefined dates when sorting of Date column in the GUI; the Events category’s views when sorting on TYPES; the srting tool’s rules for sorting, the sorting of events in Reports.
On the other hand, I wonder how Gramps could implement such auto-sorting attributes. Sort are obvious: Birth (and its fallback events) should be before Marriage (and fallbacks) should be before Death (and fallbacks) should be before interment.
But what of the other events? Should they be mapped against significant markers in a life’s timeline? Such as events that should be after puberty and before old age. While others would use the context of other events. Such as offspring events after marriage and before parent deaths.
It brings to mind discussions of the complexties of “strange attractors” in mathematics.
I was thinking that assigning a sortable “Priority” field to each Person Event type could work, for example…
00 for Birth Events
02 for Baptism Events
10 for Education Events
15 for Military Events
20 for Vocational Events
etc til …
98 for Death Events
99 for Burial Events
Of course, even better would be allowing the user to dynamically re-assign default priority groups, so that the groupings could be varied based on the user’s needs at the time.
I will add this suggestion to Ideas. That portion of the thread has been moved to Ideas.