# New module: Show all related objects (and how they relate). Looking for feedback

**URL:** <https://www.dolibarr.org/forum/t/new-module-show-all-related-objects-and-how-they-relate-looking-for-feedback/30817>\
**Category:** Developing for Dolibarr\
**Created:** [December 4, 2025, 12:27am UTC](https://www.dolibarr.org/forum/t/new-module-show-all-related-objects-and-how-they-relate-looking-for-feedback/30817 "2025-12-04T00:27:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![svewa](https://www.dolibarr.org/forum/letter_avatar_proxy/v4/letter/s/5f9b8f/32.png) [@svewa](https://www.dolibarr.org/forum/u/svewa)\
**Post date:** [December 4, 2025, 12:27am UTC](https://www.dolibarr.org/forum/t/new-module-show-all-related-objects-and-how-they-relate-looking-for-feedback/30817/1 "2025-12-04T00:27:07Z")

</div>

Just finished my first module, fixing what annoyed my in dolibarr since when I started using it in 2021.

To go from proposal to invoice, there is no fixed way, as it depends on _how_ you created the invoice (directly from the proposal, or from a shipping or whatever). Default dolibarr only shows direct parents and child objects, this module gives you the full tree!

 ![grafik](https://www.dolibarr.org/forum/uploads/dolibarrorg/original/2X/f/fedcfed23979023f89e058741f645532a963b612.png)

Full description and source code here: [GitHub - svewa/dolibarr-LinkedObjectTree: Module to replace the related objects (only parent and children) with the full tree, so you can jump to any related document directly](https://github.com/svewa/dolibarr-LinkedObjectTree)

Feel free to tell me what you think.

---

<div class="post-metadata">

**Author:** ![zachmelo](https://www.dolibarr.org/forum/user_avatar/www.dolibarr.org/zachmelo/32/9195_2.png) [@zachmelo](https://www.dolibarr.org/forum/u/zachmelo)\
**Post date:** [April 6, 2026, 8:17pm UTC](https://www.dolibarr.org/forum/t/new-module-show-all-related-objects-and-how-they-relate-looking-for-feedback/30817/2 "2026-04-06T20:17:50Z")

</div>

This looks like a great implementation and something I’ll test out in our build. This is a feature I’m constantly having to extend in my own custom modules and fixing the core element is so much more elegant.