Make table columns configurable

Registered by Gabriel Hurley

Different users may have different needs for what data is most useful to them on the overview page, and thus we should allow them to select the columns which are displayed. This would be implemented as a part of DataTables, with the table defining all possible columns and then using a modal widget to filter columns in/out. The data would then be persisted in a cookie (a minimized format for storing this data would be important so it doesn't fill up cookies when a lot of customizations are saved). Alternatively, we could explore saving data in Keystone's metadata for this type of thing...

Blueprint information

Status:
Complete
Approver:
Gabriel Hurley
Priority:
Low
Drafter:
Gabriel Hurley
Direction:
Approved
Assignee:
Ana Krivokapić
Definition:
Superseded
Series goal:
None
Implementation:
Needs Code Review
Milestone target:
None
Started by
Ana Krivokapić
Completed by
Cindy Lu

Related branches

Sprints

Whiteboard

***** 10/28/2016 [clu_] Thanks for the work here. Nearly 2.5 years, closing out. This feature is available in Angular. You can now do this using the registry and extensibility service.

[lblanchard 4-1-2014] Is there a UX design for this feature? Datatables.net has an extension that is a pretty nice, basic design (http://datatables.net/extras/colvis/). I'd be happy to help with further UX design needs too, let me know!

Gerrit topic: https://review.openstack.org/#q,topic:bp/configure-table-columns,n,z

Addressed by: https://review.openstack.org/94575
    Make table columns configurable

[david-lyle | 2014.07.23] Moving to Juno-3.

[lblanchard 2014.07.29] I've done some pattern work around tables and specifically around customizing columns in a table. I wanted to share these designs incase they are helpful to what we need in Horizon. These designs allow the user to reorder columns as well as add/remove columns that are show in the table:
https://www.patternfly.org/wikis/patterns/pattern-development/draft-patterns/data-table/#configcolumns

Please let me know if there are any questions on this design.

[david-lyle | 2014.08.28] Moving out of Juno. I think this needs some more work. It certainly would be valuable, but let's think about the implementation a little more. We may be to the point of wanting to require a server-side session store. But that raises other issues.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.