# Stillbirth events in Gramps

**URL:** <https://gramps.discourse.group/t/stillbirth-events-in-gramps/2309>\
**Category:** Development\
**Created:** [March 2, 2022, 5:03pm UTC](https://gramps.discourse.group/t/stillbirth-events-in-gramps/2309 "2022-03-02T17:03:40Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![DaveSch](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/davesch/32/40_2.png) [@DaveSch](https://gramps.discourse.group/u/DaveSch)\
**Post date:** [March 2, 2022, 8:41pm UTC](https://gramps.discourse.group/t/stillbirth-events-in-gramps/2309/2 "2022-03-02T20:41:15Z")

</div>

Here’s my Feature Request and as such would not make it into the code until 5.2 at the earliest.

> <https://github.com/gramps-project/gramps/pull/1148>
>
> Add Stillborn as a fallback event for both Birth and Death

and the discussion here.

> [@Stillborn as a coded event type](https://gramps.discourse.group/t/stillborn-as-a-coded-event-type/181):
>
> One of the custom event types I created was Stillborn. When I found a record for a stillborn child, I was always going back to find out how I handled other occurrences. Did I enter them with both Birth and Death events, only one event and which one. A lot of the inconsistency was a result of all the various ways that the events were recorded by the various locales, each doing it differently. And I am sure for some locales these records have been shunted off to a different filing cabinet never …

---

_[View the full topic](https://gramps.discourse.group/t/stillbirth-events-in-gramps/2309)._