This will require some thought, as not all facts are available for every host.

I'll keep in mind once we start redoing the basic UI

In case it wasn't clear, heres an example of a "move from A column to be B column" UI :

(uploded for Issue #82)

Even better would be and "push up" "push down" buttons so you don't need to add/remove entries to change the order.

One of the admins I know asked me exactly the same feature. He don't want the OS column but the ipaddress one instead.
Customising this list can be helpful for some admins.

Is there any activity on this?

Ive started implementing this on my own installation.

Ill start out with one column at first, IP-adress. That is extending the list view.

But Ill look into make the "Extra column" configurable, so that you could choose which value to put into the column. I think defaulting to IP-adress will be wise since the IP-adress will be available for all hosts.

- K -

I'm implementing this on a per-user basis.

Users and non-users have some sensible defaults (current properties, name, os, environment, etc..) stored in a field in the database, User - "custom_host_table", just a string that is generated through an UI similar to the one Oded Ben Ozer posted.

When an user visits http://foreman/hosts, the page will load this list of custom columns and will populate it with whatever the user has on the mentioned "custom_host_table" property, or it will load the default values if user.current is not set.

Any chance of this going upstream?

Latest foreman as of Jan 8th 2013 has something like this

What I'm doing essentially looks the same.

Daniel Lobato Garcia wrote:

I'm implementing this on a per-user basis.

Users and non-users have some sensible defaults (current properties, name, os, environment, etc..) stored in a field in the database, User - "custom_host_table", just a string that is generated through an UI similar to the one Oded Ben Ozer posted.

When an user visits http://foreman/hosts, the page will load this list of custom columns and will populate it with whatever the user has on the mentioned "custom_host_table" property, or it will load the default values if user.current is not set.

Any chance of this going upstream?

I would love to extend Settings model to include a User settings,
this way we could reuse the settings table and make settings smart enough to load the system wide defaults or the specific user settings (in general)

I think this would be the most flexible solution long term as well (for any type of settings that makes sense for a user to override).

- removed spam -

If anyone search for such functionality, there's https://github.com/theforeman/foreman_column_view
It's not per user, it's hard to setup and it's limited just to host attributes but it may help some users.