# Filter changes by one user result in inconsistent views for other users **URL:** \ **Category:** Bugs & Issues\ **Created:** [April 17, 2019, 7:36am UTC](https://community.fibery.io/t/filter-changes-by-one-user-result-in-inconsistent-views-for-other-users/212 "2019-04-17T07:36:36Z")\ **Posts on this page:** 1\ **Showing post:** 12
**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:46am UTC](https://community.fibery.io/t/filter-changes-by-one-user-result-in-inconsistent-views-for-other-users/212/12 "2019-04-17T11:46:49Z")
That’s super awesome! Exactly what I was expecting in the following post: > [@"Extended Relations" and usage in Board view](https://community.fibery.io/t/extended-relations-and-usage-in-board-view/152): > > [Edit: rewritten for clarity.] Hi, In our real-life usage, we have found that it will be very useful if the concept of type to type Relations can be extended to include “extended” relations too. For example, if type User Story is related to type Feature and type Feature is related to type Epic, then “extended relations” of an instance of User Story will include the instances of Epic related to that User Story via a Feature. In Board view, currently the configuration options for Columns/Rows … I’ll test this extensively. This will greatly reduce the number of explicit relationship to the root Type. --- _[View the full topic](https://community.fibery.io/t/filter-changes-by-one-user-result-in-inconsistent-views-for-other-users/212)._