# "Extended Relations" and usage in Board view

**URL:** <https://community.fibery.io/t/extended-relations-and-usage-in-board-view/152>\
**Category:** Ideas & Features\
**Created:** [April 3, 2019, 11:36am UTC](https://community.fibery.io/t/extended-relations-and-usage-in-board-view/152 "2019-04-03T11:36:54Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Shafqat\_Ullah](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/shafqat_ullah/32/101_2.png) [@Shafqat\_Ullah](https://community.fibery.io/u/Shafqat_Ullah)\
**Post date:** [April 17, 2019, 11:55am UTC](https://community.fibery.io/t/extended-relations-and-usage-in-board-view/152/4 "2019-04-17T11:55:11Z")

</div>

The following existing feature probably addresses this need:

> [@Filter changes by one user result in inconsistent views for other users](https://community.fibery.io/t/filter-changes-by-one-user-result-in-inconsistent-views-for-other-users/212/10):
>
> This is somewhat tricky. We have an algorithm that tries to discover relation using the whole graph. Check this structure [16%20PM] Note that Epic have direct relation to Product, so you can easily create Epics Backlog and other views. Note that Feature DOES NOT have direct relation to Product. You can still create a Features Backlog board, but it will show Features ONLY if Feature is linked to an Epic (otherwise we have no idea to which product the feature belongs).

---

_[View the full topic](https://community.fibery.io/t/extended-relations-and-usage-in-board-view/152)._
