Personal smart dashboard

Proposal

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.

Links/References

Original Issue: https://gitlab.com/gitlab-org/gitlab-ce/issues/22551

Project Smart Dashboard: https://gitlab.com/gitlab-org/gitlab-ce/issues/27112

Supporting Research

Related issues: https://gitlab.com/gitlab-org/ux-research/issues/24, https://gitlab.com/gitlab-org/ux-research/issues/5

• 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.

@lbennett shared this screenshot from Sentry in chat. It is a feedback email that they send but posting here as inspiration for the personal dashboard.

mentioned in issue #27112 (moved)

mentioned in issue #22551 (closed)

mentioned in issue #20680 (closed)

From https://gitlab.com/gitlab-org/gitlab-ce/issues/17184

Usually when i open Gitlab i want some questions answered:

• How can i help my team today?
• What was i working on yesterday/this week?
• Do i have some unfinished issues/MRs?
• What my team is doing of important now?
• What is trending in Gitlab?
• Did someone mention me?

mentioned in issue #17184 (closed)

@tauriedavis I've been thinking about this for a while and I think the most important stuff depends on the person.

For a lead it is:

• What is my team working on?
• What stuff do I need to review?

For a dev it might be:

• What do I need to work on next?
• What's the status of my work in review?

This type of dashboard would be really helpful to me, especially as my team grows larger.

@tauriedavis Dig the inspiration.

Sounds like a good weekend project for someone. I think with some major tweaking of the regular dashboard, we could make it more appealing to the mass audience. It does leave a bit to be desired. ;)

mentioned in issue #25408 (moved)

Show last change in Project on every Project overview: https://gitlab.com/gitlab-org/gitlab-ce/issues/25408

a view of all projects you have participated in, or follow, with a way to easily see what was last changed

mentioned in issue #29878 (closed)

Posting this design by @cperessini just for discussion purposes

mentioned in issue #31390 (moved)

mentioned in issue #31891 (closed)

mentioned in issue #33152 (moved)

changed the description

Supporting research section added to the issue description.

cc @tauriedavis @sarrahvesselov @victorwu

mentioned in issue #29058 (moved)

mentioned in issue #3235 (moved)

moved to gitlab#7928

Hey!

GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current gitlab-ce repository will become a read-only mirror, without any proprietary code. All development is moved to the current gitlab-ee repository, which we will rename to just gitlab in the coming weeks. As part of this migration, issues will be moved to the current gitlab-ee project.

If you have any questions about all of this, please ask them in our dedicated FAQ issue.

https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

You can also find more information here:

• https://gitlab.com/gitlab-org/gitlab-ee/issues/13304
• https://about.gitlab.com/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/

Frequently Asked Questions

For an up to date list of questions and answers, please take a look at https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

What will we do with the repository names?

https://gitlab.com/gitlab-org/gitlab-ee/ will become https://gitlab.com/gitlab-org/gitlab, and https://gitlab.com/gitlab-org/gitlab-ce will become https://gitlab.com/gitlab-org/gitlab-foss.

Why rename gitlab-ce to gitlab-foss?

Using "gitlab" and "gitlab-ce" would be confusing, so we decided to rename gitlab-ce to gitlab-foss to make the purpose of this FOSS repository more clear

I created a merge requests for CE, and this got closed. What do I need to do?

You will need to create a merge request at https://gitlab.com/gitlab-org/gitlab-ee/. This link will eventually redirect to https://gitlab.com/gitlab-org/gitlab.

How does the licensing work in this new setup?

Everything in the ee/ directory is proprietary. Everything else is free and open source software. If your merge request does not change anything in the ee/ directory, the process of contributing changes is the same as when using the gitlab-ce repository.

Will you accept merge requests on the gitlab-ce/gitlab-foss project after it has been renamed?

No. Merge requests submitted to this project will be closed automatically.

Will I still be able to view old issues and merge requests in gitlab-ce/gitlab-foss?

Yes.

How will this affect users of GitLab CE using Omnibus?

No changes will be necessary, as the packages built remain the same.

How will this affect users of GitLab CE that build from source?

Once the project has been renamed, you will need to change your Git remotes to use this new URL. GitLab will take care of redirecting Git operations so there is no hard deadline, but we recommend doing this as soon as the projects have been renamed.

Where can I see a timeline of the remaining steps?

https://gitlab.com/gitlab-org/gitlab-ee/issues/13304

Will community contributions submitted to the new "gitlab" repository be available in the new gitlab-foss repository?

Yes, these changes will be synced to gitlab-foss automatically, several times per day.

locked this issue