Skip to content

[Integrates] Allow that customers can edit the nickname of the git roots

Problem to solve

Currently, when users add git roots, platform is automatically assigning to each of them a nickname. And users, then, are not able to modify the nicknames as they want.

This situation has some benefits, like controlling that root nicknames are not repeated at org level, and also preventing that users add some special invalid characters. However, it is also causing another kind of problems for us, like:

  • Some users that want to establish a predefined format to be used to name the git roots (according to their own internal workflows and policies), and because the auto assignment is not possible
  • Users saying that the auto-assigned nicknames differs from the name of the repos, causing confusion and even causing troubles at the time to filter vulns by root nickname (via platform or via API), or using the CI agent, or even using the IDE extension
  • Users that constantly request us (via help) to change/adjust nicknames, even in batch (when there are a lot), making it more difficult to provide assistance via help desk (and even being an inconvenient type of request according to our own bussiness rules).

Intended users

Customers

Proposal

Allow that users can edit the nickname of the git roots as they want, but still establishing some validation rules on our part (to avoid inconsistences). Even it should be allowed that users can upload several root nicknames in batch (it could be, in example, via uploading a csv file)

Test plan

  • Frontend and backend validations must be the same for nickname.
  • Nickname must be unique in the organization (no other root has the new nickname).
  • When user changes the nickname only, no batch processes must be executed (like clone_roots).

Steps

Links / references

Edited by Sebastian Cardona
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information