Add ability to provide a name for webhooks
Release notes
Add ability to provide a human-readable name for a webhook you have created
Problem to solve
Right now the webhook UI can be a bit painful to work with if you have multiple webhooks defined targeted to the same endpoint...you have to click into the different hooks to figure out which one has the config you want to change. It would be nice if we could specify a name for each webhook?
Proposal
Add a field so that when you create/edit the webhook you can provide a unique, optional name. If the name is not provided, then we can use the current method when displaying webhooks in a list, otherwise it would use the name provided.
Intended users
Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later.
Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
- Allison (Application Ops)
- Priyanka (Platform Engineer)
User experience goal
When you have multiple webhooks, it is difficult to know which is which when you need to edit one.\