Add per-user column selection for Tasks and other table views

What:
Add a column selector to table-based views (Tasks, Host Pools, Session Hosts, etc.) that allows users to:

  • choose which columns are visible
  • reorder columns
  • save multiple named views per user

Value:
This would make the UI far more adaptable to real-world workflows, where a single administrator often shifts between different roles (e.g., scripting, troubleshooting, help desk, reporting) throughout the day.

Instead of forcing one static layout, users could instantly switch between purpose-built views that match what they’re trying to accomplish in that moment.

How it should work:

Add a Columns / Customize Columns control with the ability to:

  • Show/hide columns
  • Reorder columns
  • Save the current configuration as a named view
  • Switch between saved views
  • Reset to default

Views should be:

  • Per-user (not global)
  • Quickly switchable (dropdown or tabs)
  • Persisted across sessions

Example:

A single admin may use multiple views throughout the day:

“Scripting / Validation” view:

  • Task Name
  • Resource Name
  • Status
  • Result
  • Duration

“Troubleshooting” view:

  • Task Name
  • Status
  • Start Time
  • End Time
  • Result

“Help Desk” view:

  • User / Initiated By
  • Resource Name
  • Status
  • Date

“Reporting / Audit” view:

  • Task Name
  • Scope (Workspace / Host Pool)
  • Date
  • Duration
  • Outcome

Instead of constantly reconfiguring columns, the admin can switch views instantly depending on context.

Why this matters:
Different roles need different data—but more importantly, the same person often operates in multiple roles throughout the day.

A single static column configuration doesn’t reflect how Nerdio is actually used in practice.

Allowing saved views would:

  • reduce friction when switching tasks
  • improve efficiency for power users
  • make large datasets easier to work with
  • align with how admins naturally think (task-oriented, not layout-oriented)

Related idea:
This becomes even more powerful when combined with:

  • a Result column for task output
  • an aggregated Scripted Action runtime view

At that point, users can create highly targeted views for automation validation, troubleshooting, and reporting.

0

Comments (0 comments)

Please sign in to leave a comment.