Create/Edit Release: make sure `(optional)` is applied to forms correctly

Problem to solve

Verify if the form fields of the Create/Edit Release need clean up to make sure (optional) is applied correctly.

Intended users

• Rachel (Release Manager)
• Devon (DevOps Engineer)
• Anyone involved in creating Releases with GitLab

Further details

According to Pajamas, we default to all information being required unless stated otherwise with (optional) added to the label of the corresponding input field.

In !28493 (comment 321302921) we discussed the (optional) vs (required) labels for the form fields of Release Assets, aka Links. We want to make sure that the Create/Edit Release form fields have the (optional) label added whenever necessary, so that users experience a consistent way of filling out the form.

Proposal

Add * Required to the label of the Tag field:

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

No

Links / references