Convert explorers to non-explorer style screens

[h-kataria]

Remove the trees on the left side, so basically convert all explorers into non-explorer screens. Tree should be in its own view, can be accessed from a toolbar button or a second level menu item, maybe something similar to Topology menu item. A screen of its own where user can view objects in a tree.
Total of 16 explorers, that have 53 accordions (each accordion has its own tree)

In order to De-explorize the explorers listed below, as a first step we are going to split the accordions in each explorer into their own explorer and then de-explorize them individually this makes it easier to test/review and merge individual PRs. This work can be tracked here

Legend

• Level 1 Menu Item
  • Level 2 Menu Item (Optional based on nesting)
    • Level 3 or Level 2 Menu Item (Explorer)
      • Accordions under Explorer

List of All Explorer style screens in UI

• Overview
  • Chargeback
    • Reports
    • Rates
    • Assignments
  • Reports
    • Saved Reports
    • Reports
    • Schedules
    • Dashboard
    • Dashboard Widgets
    • Edit Reports Menus
    • Import/Export
  • Utilization
    • Utilization
• Services
  • My Services -De explorization of Service Pages #8229
    • Services
  • Catalogs
    • Service Catalogs
    • Catalog Items
    • Orchestrations Tmplates
    • Catalogs
  • Workloads
    • VMs & Instances
    • Templates & Images
• Compute
  • Clouds
    • Instances
      • Instances by Provider
      • Images by Provider
      • Instances
      • Images
  • Infrastructure
    • Virtual Machines
      • VMs & Templates
      • VMs
      • Templates
    • Datastores
      • Datastores
      • Datastore Clusters
    • PXE
      • PXE Server
      • Customization Templates
      • System Image Types
      • ISO Datastores
    • Networking
      • Switches
• Reorganizing Configuration/Automation Menu items Automation/Configuration menu reorganization #7657
• Configuration
  • Management
    • Providers
    • Profiles
    • Configured Systems
• Automation
  • Ansible Tower
    • Explorer
      • Providers PR
      • Configured Systems PR
      • Templates PR
  • Automate
    • Explorer
      • Datastore
    • Customization
      • Provisioning Dialogs
      • Service Dialogs
      • Buttons
      • Import/Export
• Control
  • Explorer
    • Policy Profiles
    • Policies
      • Other sub menus under Control that shared code with MiqPolicyController was split into their own controllers
        • Control Import/Export
        • Control Simulation
        • Control Log
    • Events
    • Conditions
    • Actions
    • Alert Profiles
    • Alerts
• Settings/Application Settings (OPS)
  • Settings
  • Access Control
  • Diagnostics

Completed items (with strikethrough) per release:

• Jansa
• Lasker

[h-kataria]

Non Explorer style screen, with filters in the listnav on the left

Explorer style screen with tree and accordions on the left

Listnav on summary screen that shows same data as shown on the right side

Listnav on list views showing filters/searches(default filters and user created filters)

Listnav on list view when there are no filters

Listnav on a child list view thru relationship

[chessbyte]

should Configuration be added to the list in the opening comment and perhaps convert it to a checklist?

[h-kataria]

should Configuration be added to the list in the opening comment and perhaps convert it to a checklist?

yes, that's a good idea, will do that.

[chadh1313]

Priority preferred for:

• chargeback (rates, assignments)
• chargeback (reports)

Additionally, also request ability to deep-link directly to tabs such as rates, assignments.

[chessbyte]

@h-kataria next priority is Policies (targeted for the Kasparov release)

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.