Duplicate: Add comment field to Project and Group Access tokens
Release notes
Comment fields for Project and Group Access Tokens
GitLab now lets you add a comment to project and group access tokens to allow for succinct display names while maintaining the full context for why a token was created.
Problem to solve
As someone who manages tokens for a variety of projects, I'm faced with a tradeoff:
- use a descriptive name (for example, the URL to the project where a specific Project Access Token or Group Access Token is used) or a friendly display name. This is specifically challenging for tokens used to create issues in projects as the email notifications and issue titles can have long and ugly display names for the tokens that created such issues.
Proposal
Add an additional (optional) field for Project and Group access tokens. This would mean:
- Token name -> Display name
- Token comment -> Enter any information that will be helpful to describe this token. For example, the application using the token or the purpose of the token. Do not give sensitive information for the name of the token, as it will be visible to all project members.
Intended users
- Sidney (Systems Administrator)
- Rachel (Release Manager)
- Allison (Application Ops)
- Ingrid (Infrastructure Operator)
- Amy (Application Security Engineer)
- Alex (Security Operations Engineer)
- Cameron (Compliance Manager)
Feature Usage Metrics
Non-nil
values in the field where the comment would be stored.
Does this feature require an audit event?
Nothing new - token creation is already audited.