Error messages on Release creation are unclear

Intended users

Problem to solve

Error message on Release page when there's already a release associated with the selected tag is generic and does not point the user to a solution

User quote from UX Scorecard
“This error message is really frustrating. It just told me it went wrong” (see insights)

image

User experience goal

The user should be able to see they selected an invalid option before they submit the form to create the release.

Proposal

  1. Introduce a validation error informing the user their selected tag is already associated to another release when they select it on the dropdown
  2. While the validation error is showing, the submit button (Create release) should be disabled

1.1__release-tag__error-message--no-link

2.1__release-tag__error-message--detail--no-link

Validation text:

Selected tag is already in use. Choose another option.

Permissions and Security

No changes are expected to the current permission models or security considerations

Documentation

Availability & Testing

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

Reduce pain-points raised by users during UX Scorecards and usability testing about error messages in release creation to 0.

What is the type of buyer?

Skyler - the Chief Information Security Officer

GitLab Core

Is this a cross-stage feature?

No

Links / references

gitlab-design#1670 (closed)

Edited by Daniel Fosco