User Settings Storage

[michaelkleinhenz]

Description

As a user, I want to have settings and other UI-based data (like custom filters) stored on my account and being available on later visits.

Acceptance Criteria

• User settings are transparently stored on server side on the User.
• User settings can be retrieved and updated from any client component.
• Client components should be able to create new settings using a context and a key on demand.
• The user can view and update his current user settings using a dialog view.

Note: This story covers all user-specific settings, cross-component ones as well as component-specific ones.

Note: This story may require an API that makes the settings UI for the user dynamic by requiring a client component giving a full description of the settings, including help strings, available values etc. The key is that a component should be able to create new setting keys on demand.

Relationships

Put linked Team/Product story links here

[joshuawilson]

@michaelkleinhenz I think this is something the Platform team should own. All the teams/components need this but they shouldn't set it up. Can we move this to the Platform backlog?

[michaelkleinhenz]

Sure. This is the intention. We need to consolidate crossover stuff. Also, everything in here has to end up in the master OSIO backlog. Derived sprint-long stories should be ending up in the teams backlogs (as it was till now, no change there). This level is PM communication level only.