Tooltips for collapsed Issue/Merge Request sidebar

This issue came from: https://gitlab.com/gitlab-org/gitlab-ce/issues/24805#note_19037117

The current state of tooltips on the collapsed sidebar is poor:

Proposal

We should improve it by:

• Tooltips on:
  • Assignee icon
    • No Assignee: Assignee
  • Milestone icon
    • Milestone set with experiration date: Currently it shows how many days remaining, perhaps we should change it to Milestone: 25 days remaining
    • Milestone set, but no expiration date set: Milestone
    • No milestone set at all: Milestone
  • Timetracking icon
    • No time tracking: Time tracking
    • With time spend or an estimate : Time tracking (perhaps give an exact time spent/estimate in tooltip..like we do with human readable time notations)
  • Due date icon
    • No due date or with due date: Due date
  • Labels icon
    • No labels: Labels
    • With labels: Labels: Frontend, UX
  • Participants icon
    • As there is always a minimum of 1 participant: Participants
  • Notification icon
    • Subscribed or unsubscribed to issue/mr: Notifications
  • Reference Clipboard icon (This is part of https://gitlab.com/gitlab-org/gitlab-ce/issues/23570#note_17652384)
    • Tooltip should state: Copy reference to clipboard

cc: @cperessini @tauriedavis @awhildy

Mentioned in issue #24805 (closed)

This would be great to have

I think if an item doesn't have a value, we should explicitly say that. For example, if there are no labels assigned, we should say No labels instead of just Labels. That way you know the exact information without having to expand the sidebar.

@dimitrieh What do you think?

@cperessini nice!

I however do not think that one is necessary perse :) as we will already have the "zero" count under the labels if none is applied. Agreed?

@dimitrieh Right! I was so focused on looking at the tooltips that I forgot we already have that information available

moved to gitlab#7207

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

mentioned in merge request !14785