What's in development for Gramps 6.2

We are very close to the Gramps 6.1 release. You can see the technical contributions already accepted (“Closed”) and considered (“Open”) here: GitHub · Where software is built

What’s next? Here are the features and improvements being considered for Gramps 6.2 that is planned to be released in Oct 2026. Is there something big that hasn’t been started yet that you are hopeful for? Let us know.

New Calendar Support

  • #2369 — Chinese Lunar Calendar (农历)
  • #2374 — Vietnamese Lunar Calendar (Âm Lịch)
  • #2375 — Korean Lunar Calendar (음력)
  • #2376 — Japanese Imperial Era (和暦)

User Experience / Onboarding

  • #2394 — First-run onboarding tour with step-by-step popovers
  • #2388 — Prompt new users to import the Example Family Tree on startup
  • #2377 — Add an info button to the date editor with calendar/syntax help
  • #2214 — Simplified Interface (reduce complexity)

Data Entry & Editing

  • #2338 — Add Separation event type and related family types
  • #2372 — Add Event and Citation table support to CSV importer
  • #2351 — Display images according to Exif orientation tag
  • #2269 — Quick Add bar in Select Place dialog for comma-separated hierarchy entry
  • #2267 — “New” button in Place, Source, and Citation selector dialogs
  • #2296 — Show date format examples in Preferences Data tab
  • #2165 — Save filter dates in locale-independent format
  • #2141 — Coalesce event role types (schema change + upgrade)

Views & Display

  • #2217 — Spousal labels in the Relationships view based on family type
  • #2215 — Support for multiple named dashboards
  • #2223 — Place Cloud gramplet
  • #2164 — Better default Tag colors

Clipboard & Sessions

  • #2273 — Persist clipboard across sessions; filter view by active database
  • #2299 — Allow gui.clipboard to import without a default screen

Filters

  • #2305 — Drag-to-reorder UI for rules in the filter editor
  • #1963 — Allow filters to be cancelled

Performance

  • #2324 — Push include_classes filter into SQL (schema change)
  • #2229 — Reduce number of DB queries on open/close
  • #2178 — Add JSON field indexes on json_data handles (schema change)
  • #2177 — API for overriding filter rules on DB backends
  • #2160 — Optimizer: skip loop when all rules are optimized
  • #2111 — Graph algorithms improvements
  • #2109 — Database config

Plugin System

  • #2252sniff_function support to ImportPlugin for version-aware dispatch
  • #2250 — Allow requires_mod entries to specify pip package name and version
  • #2220 — Add SIDEPANEL plugin type for pluggable right-side panels

Infrastructure & Build

  • #2192 — PyInstaller-based Windows All-in-One (AIO) build
  • #2289 — Specify the required GTK version
  • #1988 — Fix man page updates

Reports

  • #2208 — Major upgrade to Latexdoc report
  • #2050 — Fix icu/PyICU exception handling in Narrated Web report
  • #2142 — Subdirectories and comments in Narweb CSS files

Code Quality / Type Hints

  • #2233 — Modernize type hints across the codebase
  • #2232 — Additional type hinting for DB-related classes
  • #2184 — Add type hints to gen/lib classes and fix filter rule type errors
  • #2128 — Protocols for typing of Gramps objects

Bug Fixes

  • #2237 — Fix resource leaks
  • #2195 — Refactor proxy system: two-layer include/sanitize filtering
  • #2149 — Add resilience to set_birth_death_index() for storage backend failures

Relationship Tools

  • #1882 — Refactor Relationship Calculator and add a search bar

48 open items as of 2026-06-20. Source: GitHub · Where software is built

A field for entering URL - mostly needed for source/citations. This has been asked for several times.

NB! I don’t want to start a discussion here, whether URL links are stable or not, thanks.

This has been proposed as part of the implementation of CSL which has variables for both the url and the date it was accessed. I think that @StoltHD was also interested in this.

If you are interested in what “CSL” is, read this: Citation Formatter - #10 by Nick-Hall

tl;dr

CSL - Citation Style Language