#140: User-defined dashboard contents.
-------------------------+-------------------------------------------------
Reporter: olemis | Owner: nobody
Type: | Status: new
enhancement | Milestone:
Priority: minor | Version:
Component: dashboard | Keywords: dashboard configuration database
Resolution: | markup preferences admin
-------------------------+-------------------------------------------------
Comment (by jdreimann):
From the description this seems to be a way to allow for more modifiable
widgets, which could also be added or removed at will by the user.
I believe that any such system should be some way out - it needs a certain
stability of what the user can expect in each widget, nevermind a
collection of worthwhile widgets, and a clear upgrade path should the
dashboard change significantly.
There are more reasons: Users may dismiss a widget early on because it
doesn't yet provide the functionality they expect, and not revisit it
later. To my knowledge evidence suggests that users do not regularly
assess all available options and rationally decide on which ones to
choose, which makes this a potentially very complicated system to maintain
and support for a small proportion of users.
The ultimate argument I see against this at this time though is that #138
already provides similar functionality and challenges. If we're committed
to fixing them, we may as well start there first.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/140#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
