#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 gjm):
Replying to [comment:4 olemis]:
> Besides please consider reading [http://mail-
archives.apache.org/mod_mbox/incubator-bloodhound-dev/201207.mbox
/%3ccagmzauob-rz9+umfgd7krg-wn+1ea-_w5x2ltoenh7ch5rv...@mail.gmail.com%3e
this message] actually started by Gary and related to role-specific (e.g.
user groups) dashboards and other similar use cases , IMO requiring extra
flexibility.
I'm afraid that I am not convinced by this argument. Putting all the
functionality into the single dashboard view was not what I was
advocating. In the long run it may be seen as worthwhile to provide this
flexibility but my suggestion was to provide different standard views.
Part of the advantage of this would be that a user should not need to
discover or build the most appropriate dashboard for themselves yet. We
can provide more standard views that everyone (or at least everyone with
appropriate permissions) can view.
I think it would be better to shelve this discussion until a point at
which we are ready to consider further generalisation of the dashboard. It
is not that it is completely undesirable but there are more important
things to get on with.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/140#comment:5>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
