Answers.Body: <p>I agree that we need hierarchical display but it's not yet possible in SearchKit.</p>
  <p>However, if you prefer the old implementation, it's quite easy to disable the new one (and keeping AdminUI) by changing the page route (url) of the corresponding FormBuilder :</p>
  <p><a href="https://i.sstatic.net/nlw6e.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/nlw6e.png" alt="enter image description here" /></a></p>
  <p><a href="https://i.sstatic.net/2fX0p.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/2fX0p.png" alt="enter image description here" /></a></p>
  <p><a href="https://i.sstatic.net/hcAEJ.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/hcAEJ.png" alt="enter image description here" /></a></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-01-09T16:24:53.377Z
Answers.LastActivityDate: 2024-01-09T16:24:53.377Z
Answers.UserDisplayName: samuelsov
Answers.Body: <p>Great! That's why we created AdminUI rather than putting things directly into core - so you can kick the tyres and we can improve the new searches before they replace core functionality.</p>
  <p>Many setups don't use parent/child groups at all.  For others such as yours, they are a significant feature.</p>
  <p>There are a couple of ways you can help:</p>
  <ol>
  <li>Ideally, install a copy of master (so you have the latest SearchKit/FormBuilder/AdminUI), make changes to the Groups search and create a PR.</li>
  <li>If you don't want to create a PR yourself, see the notes at the top of the <a href="https://lab.civicrm.org/dev/core/-/issues/3912" rel="nofollow noreferrer">AdminUI tracking issue</a></li>
  <li>If you can't get implement the changes you'd like to see then <a href="https://lab.civicrm.org/dev/core/-/issues/new" rel="nofollow noreferrer">create a gitlab issue</a> and describe how you think it should work. It is more useful to specify positively what it should do rather than just &quot;It's a mess&quot;:-).  Note that we don't have expanding hierarchy functionality yet so things we can implement with its current abilities are more likely to happen soon.</li>
  </ol>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-01-10T18:14:57.073Z
Answers.LastActivityDate: 2024-01-10T18:14:57.073Z
Answers.UserDisplayName: Aidan
Body: <p>AdminUI comes bundled with CiviCRM - when enabled, it does a pretty great job on most pages - but on groups - I hate it. (I do like the search functionality though)</p>
  <ul>
  <li>It ignores hierarchy (parents, sub parents, children, etc) are all mixed in together - We have about 20 active parent groups at any given time - with maybe 100 active groups total. Parent groups are helpful to be organized or to see all related groups in one place.</li>
  <li>When searching for parent groups - it searches for all groups - not just ones listed as parents (or those that have &quot;children&quot;). Users have to remember the exact name of the parent group.</li>
  <li><s>It breaks breadcrumbs. <em>CiviCRM &gt; CiviCRM &gt; FormBuilder &gt; Edit Form &gt; Manage Groups</em> - though this seems to be an issue throughout AdminUI. TBH the original breadcrumb wasnt that useful anyways, (it was just <em>CiviCRM</em>) but at least it wasn't misleading. </s></li>
  </ul>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-01-08T16:43:39.203Z
Comments.Text: FYI the breadcrumb issue was fixed a couple releases back. Which version of Civi are you using?
Comments.UserDisplayName: Coleman
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-01-08T17:09:04.990Z
Comments.Text: 5.65.1 - updating now to 5.69.1
  Do core extensions only update with civicrm updates?
Comments.UserDisplayName: themak
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-01-08T18:06:36.930Z
Comments.Text: Yes, that's right, because the core extensions are bundled with core that's the only way to update them.
Comments.UserDisplayName: Coleman
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-01-09T16:50:09.070Z
Comments.Text: Regarding the second point, adding a filter to search only for parent or children should be doable but I think it currently behave the same as the legacy manage group page. The parent autocomplete filter is meant to get all groups which are children of the given parent.
Comments.UserDisplayName: samuelsov
Tags: <groups><formbuilder><admin><ui>
Title: AdminUI Display of Groups is Cluttered - How can we improve?
ThreadText: # AdminUI Display of Groups is Cluttered - How can we improve?
  
  (Asked by: username_0 on 2024-01-08)
  
  AdminUI comes bundled with CiviCRM - when enabled, it does a pretty great job on most pages - but on groups - I hate it. (I do like the search functionality though)
  
  * It ignores hierarchy (parents, sub parents, children, etc) are all mixed in together - We have about 20 active parent groups at any given time - with maybe 100 active groups total. Parent groups are helpful to be organized or to see all related groups in one place.
  * When searching for parent groups - it searches for all groups - not just ones listed as parents (or those that have "children"). Users have to remember the exact name of the parent group.
  * ~~It breaks breadcrumbs. *CiviCRM > CiviCRM > FormBuilder > Edit Form > Manage Groups* - though this seems to be an issue throughout AdminUI. TBH the original breadcrumb wasnt that useful anyways, (it was just *CiviCRM*) but at least it wasn't misleading.~~
  
  **Tags:** groups, formbuilder, admin, ui
  
  > **Comments:**
  > **username_1**: FYI the breadcrumb issue was fixed a couple releases back. Which version of Civi are you using?  
  > **username_0**: 5.65.1 - updating now to 5.69.1 Do core extensions only update with civicrm updates?  
  > **username_1**: Yes, that's right, because the core extensions are bundled with core that's the only way to update them.  
  > **username_2**: Regarding the second point, adding a filter to search only for parent or children should be doable but I think it currently behave the same as the legacy manage group page. The parent autocomplete filter is meant to get all groups which are children of the given parent.  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2024-01-09. Score: 1
  
  I agree that we need hierarchical display but it's not yet possible in SearchKit.
  
  However, if you prefer the old implementation, it's quite easy to disable the new one (and keeping AdminUI) by changing the page route (url) of the corresponding FormBuilder :
  
  [![enter image description here](https://i.sstatic.net/nlw6e.png)](https://i.sstatic.net/nlw6e.png)
  
  [![enter image description here](https://i.sstatic.net/2fX0p.png)](https://i.sstatic.net/2fX0p.png)
  
  [![enter image description here](https://i.sstatic.net/hcAEJ.png)](https://i.sstatic.net/hcAEJ.png)
  
  
  ---
  
  ### Answer by username_3 on 2024-01-10. Score: 0
  
  Great! That's why we created AdminUI rather than putting things directly into core - so you can kick the tyres and we can improve the new searches before they replace core functionality.
  
  Many setups don't use parent/child groups at all. For others such as yours, they are a significant feature.
  
  There are a couple of ways you can help:
  
  1. Ideally, install a copy of master (so you have the latest SearchKit/FormBuilder/AdminUI), make changes to the Groups search and create a PR.
  2. If you don't want to create a PR yourself, see the notes at the top of the [AdminUI tracking issue](https://lab.civicrm.org/dev/core/-/issues/3912)
  3. If you can't get implement the changes you'd like to see then [create a gitlab issue](https://lab.civicrm.org/dev/core/-/issues/new) and describe how you think it should work. It is more useful to specify positively what it should do rather than just "It's a mess":-). Note that we don't have expanding hierarchy functionality yet so things we can implement with its current abilities are more likely to happen soon.
  
  
  ---
  
  