### Problem to solve Adding a Release's name is only possible through the [Release Links API](https://docs.gitlab.com/ee/api/releases/links.html) ### Intended users * [Rachel (Release Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#rachel-release-manager) * [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) ### Further details Enable the new field to the ["Create Release" page](https://docs.gitlab.com/ee/user/project/releases/#editing-a-release) that allows a user to add the release name in the backend. ### Proposal > As a Release Manager, I want to add a title to my release, so that I can specify a name different from the Tag name to people that will consume the released item. 💎 [SEE PROTOTYPE ON THE `DESIGN` TAB](https://gitlab.com/gitlab-org/gitlab/issues/208317/designs/release-title.png) **Acceptance criteria:** * While creating a release using GitLab's UI, the user sees a new `Release title` the form field. * User should be able to enter all special alphanumeric characters into the field. * Entering a release title will populate the API attribute `name`. * The field is optional. * After saving the item, if a title is entered, it should render in the Release page overview/detail. ### Permissions and Security <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)?--> ### Documentation Yes, this will need a documentation update, ### Availability & Testing <!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier. What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance. * Unit test changes * Integration test changes * End-to-end test change See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### What is the type of buyer? <!-- Which leads to: in which enterprise tier should this feature go? See https://about.gitlab.com/handbook/product/pricing/#four-tiers --> ### Links / references