Don't modify casing of project topics values
Release notes
Problem to solve
When GitLab shows project topics (formerly tags) on project pages, it makes various modifications to the topics' text. As a user, I find it frustrating that GitLab makes any modifications at all. I want GitLab to show project topics in the same way that I entered them.
Intended users
- Parker (Product Manager)
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
User experience goal
When a user enters one or more topics for a project, GitLab should show the topics on the project page in the same way that they were entered.
Proposal
GitLab should not modify the values of project topics when they are displayed on project pages.
Further details
GitLab appears to apply some basic heuristics when displaying project topics. Hyphens in topic names are replaced with spaces. Space are inserted for camel cased values. And, all the space separated words are title cased.
| Topic Name Entered | Topic Name Displayed on Project Page |
|---|---|
| AWS ECS | Aws Ecs |
| aws-ecs | Aws Ecs |
| PyCharm | Py Charm |
| TF Module | Tf Module |
In all these cases, I would much prefer that GitLab display the topics as entered. The altered forms destroy acronyms (AWS), split out names that should stay together PyCharm, and create ambiguity (both AWS ECS and aws-ecs become Aws Ecs).
Additionally, when there are more topics than can be shown on the page, the tooltip for + X more shows the unaltered value (e.g., TF Module or PyCharm) instead of what would be shown on the page (Tf Module or Py Charm), which is inconsistent.
Topics entered in project general settings:
Topics as shown on project page:
Notice how the tooltip shows the original, unaltered topic values.
Permissions and Security
Project labels (tags) can be modified by developers, maintainers, and owners.
-
Add expected impact to members with no access (0) -
Add expected impact to Guest (10) members -
Add expected impact to Reporter (20) members -
Add expected impact to Developer (30) members -
Add expected impact to Maintainer (40) members -
Add expected impact to Owner (50) members
Documentation
Availability & Testing
What does success look like, and how can we measure that?
GitLab project pages should display project topics in their original form. The topic names should not be mangled or made ambiguous.