Enable service tree in classic UI

[eggoide]

Hi all, is it possible to re-enable service tree that has been in Najdorf but not in the later releases?
Thank you for any advice!

[Fryguy]

In the latest releases Services -> My Services is now a grid view, which is searchable. We had a lot of performance problems with the old tree view, especially when you had thousands of services.

[Fryguy]

That's strange and I would consider that a bug - can you open an issue in manageiq-ui-classic?

[jrafanie]

@GilbertCherrie can you take a look at this? Thanks!

[GilbertCherrie]

I wasn't able to find any issues with the search bar. @eggoide feel free to open an issue if you can find any issues along with steps to reproduce.

[CCoupel]

All,
I do agree with the need of the tree view.
Filter are good, but does not provide an elegant view. For exemple, let's say that we have a root service that represent a Project, then as children, some projects that represents the environments, and each have as children other services that provision VMs+any ansible playbook services.

If the main reason is for performance issue, can we imagine the possibility to activate/deactive the feature by accepting the performance issue?

[Fryguy]

This is an interesting perspective that I could consider. @CCoupel Can you open an enhancement request with this description? I'm not sure if we would bring it back exactly the same way, but it's possible we could come up with a performant way to still present this kind of structural view.

Note that performance wasn't the only reason for removing it, but it was the driving factor. For example, we are trying to remove the tree view component itself, because those trees are legacy angular components that we need to switch to react.

[CCoupel]

@Fryguy Thank you for your answer.
RFE done: ManageIQ/manageiq-ui-classic#9253
I still have a global question: As a ex RedHater, specialized on Cloudform for 5 years, I use to manage services as hierarchical ones; based on the Peter's book documentation; I would like to know how these customers managed the upgrade by loosing this required feature.