# CHANGELOG: February 25 / Hierarchical Lists (beta), some improvements **URL:** \ **Category:** Changelog\ **Created:** [February 25, 2021, 5:35pm UTC](https://community.fibery.io/t/changelog-february-25-hierarchical-lists-beta-some-improvements/1403 "2021-02-25T17:35:55Z")\ **Posts on this page:** 1\ **Showing post:** 20
**Author:** ![rothnic](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/rothnic/32/1850_2.png) [@rothnic](https://community.fibery.io/u/rothnic)\ **Post date:** [March 1, 2021, 3:06pm UTC](https://community.fibery.io/t/changelog-february-25-hierarchical-lists-beta-some-improvements/1403/20 "2021-03-01T15:06:26Z")
> [@mdubakov](#): > > Project Type does not have relations to Issue Type single select and system has no chance to display it **My request is to support many to many relationships**. In this example I’m only referencing types imported via the JIRA integration. There are no single selects utilized for the JIRA integration iirc. I used the auto-linking to make sure there is an association between the Issue Type and Projects. If there is a work-around of some kind, I’d be interested… I just can’t find one. > [@Chr1sG](#): > > so I think his request is that hierarchical lists support many-to-many relations (as well as one-to-many). > > It was just me that introduced single-selects into the discussion, confusing things, sorry… That is correct, but the suggestion was helpful. I haven’t looked too closely at single selects mainly because I’ve stayed away from them in other tools, where they can be more limiting. If there was a way to assign a single select, similar to the auto-linking of types, then it would be an option for me. The real reasoning on why I used a proper Type for “Issue Type” example is just because that is how it comes in via the JIRA integration. --- _[View the full topic](https://community.fibery.io/t/changelog-february-25-hierarchical-lists-beta-some-improvements/1403)._