Personal smart dashboard: Discovery
At the 2017 Mexico Summit, we brainstormed some on what an user specific dashboard would look like.
Personal Dashboard Goals (/dashboard)
- Content is customized to the user
- I can, at a glance, know what is most important for me to look at across all of my groups and projects
- The dashboard feels customized to who I am and my role, showing me the information I care about
Scans of our notes and ideas can be found here: https://drive.google.com/drive/folders/0B-PqsmU0p5QVVE1uM3JyOUtQZ0E?usp=sharing. Unfortunately we didn't have time to do as much sketching as we did for the project dashboard, but these notes can still be helpful as we did into this more.
Original Issue: https://gitlab.com/gitlab-org/gitlab-ce/issues/22551
Project Smart Dashboard: https://gitlab.com/gitlab-org/gitlab-ce/issues/27112
%11.6: prototype and user testing
%11.7: full design proposal
Personal dashboard users are developers/people actively contributing to projects. Team Leads and Directors have different/additional dashboard requirements (as documented in https://gitlab.com/gitlab-org/gitlab-ce/issues/37195 and https://gitlab.com/gitlab-org/gitlab-ee/issues/3277)
Users want to be able to see "everything that has happened whilst I was away" and "everything associated with me".
A personal dashboard should allow users to see activity which has occurred across multiple repositories on one screen. Users should be able to select which repositories they want to be displayed on the dashboard.
Users should be able to customise the type of activity they want to see (issue, merge requests, etc) on the dashboard. This customisation should be offered on a per repo basis. For example, a user may want updates related to issues and merge requests for Repository A and issues only for Repository B.