# Parent item Revisions no longer show nested/relational deltas after v11.17.0 (translations / O2M) — regression or intentional? Looking for guidance

**URL:** <https://community.directus.com/t/parent-item-revisions-no-longer-show-nested-relational-deltas-after-v11-17-0-translations-o2m-regression-or-intentional-looking-for-guidance/2447>\
**Category:** Help\
**Tags:** data-modeling\
**Created:** [August 6, 2026, 5:03am UTC](https://community.directus.com/t/parent-item-revisions-no-longer-show-nested-relational-deltas-after-v11-17-0-translations-o2m-regression-or-intentional-looking-for-guidance/2447 "2026-08-06T05:03:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Norman\_Chan](https://sea2.discourse-cdn.com/flex002/user_avatar/community.directus.com/norman_chan/32/160_2.png) [@Norman\_Chan](https://community.directus.com/u/Norman_Chan)\
**Post date:** [August 6, 2026, 5:03am UTC](https://community.directus.com/t/parent-item-revisions-no-longer-show-nested-relational-deltas-after-v11-17-0-translations-o2m-regression-or-intentional-looking-for-guidance/2447/1 "2026-08-06T05:03:09Z")

</div>

### Describe the Bug / Question

After upgrading from **Directus v11.6.0 → v11.17.0** , the **Revisions → Updates Made** panel on a parent item only shows **top-level / scalar** field changes.

Nested / relational changes that used to appear in the parent revision delta (e.g. **translations** multilingual edits, other O2M/M2M nested payloads) are **no longer visible** on the parent item.

We understand this may be related to the intentional change in **v11.17.0** :

- Release notes: [v11.17.0](https://github.com/directus/directus/releases/tag/v11.17.0) — “Fixed revisions not using prepareDelta” ([#26867](https://github.com/directus/directus/pull/26867))
- That PR includes **“omit relational fields from revision data”** (also tied to GHSA-mvv8-v4jj-g47j)

Older discussion/issue around translations + revisions (v10 era):

- [#22881](https://github.com/directus/directus/issues/22881) / [Discussion #22886](https://github.com/directus/directus/discussions/22886)

Those are from 2024 and predate the 11.17 delta sanitization. We’d like **current official guidance** for v11.17+:

1. Is omitting nested relational payloads from the **parent** revision delta **intentional and permanent** for security / correctness?
2. Is the recommended way to audit nested edits to inspect **child collection revisions** (e.g. `*_translations`) and/or revisions linked via `parent`?
3. Is there (or will there be) a supported way to **surface nested diffs in the parent Revisions UI** without storing full relational payloads back into the parent `delta` (e.g. aggregating child revisions)?
4. Is there any config / env / accountability setting to restore the pre-11.17 parent “Updates Made” behavior? (We assume no, but want confirmation.)

This is primarily a **product / security policy question** , but it also feels like a **UX regression** for editors who relied on parent Revisions to review translation and relation changes.

### To Reproduce

1. On Directus **v11.6.0** (or any build before the prepareDelta / omit-relational change):
  - Open a collection with a **translations** field (or other nested O2M).
  - Edit a translated field on an existing item and save.
  - Open **Revisions → Updates Made** on the parent item → nested translation / relation changes are visible in the delta.

2. Upgrade to **v11.17.0** (same schema / same workflow).
3. Edit translations (or other nested relations) again and save.
4. Open parent **Revisions → Updates Made** → only top-level fields appear; nested structure changes are missing.

### Directus Version

- Before: `11.6.0` (nested diffs visible on parent)
- After: `11.17.0` (nested diffs not visible on parent)

### Hosting Strategy

Self-Hosted

### Database

### Additional Context

- Accountability on the parent collection is enabled (`all` / revisions tracked).
- We can provide redacted screenshots of parent `directus_revisions.delta` before vs after upgrade if helpful.
- We are **not** asking to reintroduce a security vulnerability; we want clarity on the intended audit model for nested content after #26867, and whether a safe parent-UI aggregation of child revisions is on the roadmap.

---

<div class="post-metadata">

**Author:** ![Beth](https://sea2.discourse-cdn.com/flex002/user_avatar/community.directus.com/beth/32/30_2.png) [@Beth](https://community.directus.com/u/Beth)\
**Post date:** [August 6, 2026, 10:51am UTC](https://community.directus.com/t/parent-item-revisions-no-longer-show-nested-relational-deltas-after-v11-17-0-translations-o2m-regression-or-intentional-looking-for-guidance/2447/2 "2026-08-06T10:51:04Z")

</div>

Hi @Norman_Chan, all issues like this need to be opened on [GitHub](https://github.com/directus/directus/issues) please. If you wouldn’t mind copying the shared information over there, you’ll be able to be kept updated. Thanks, Beth