Automatic "tag > release" creation behavior is not clear enough for users
Problem to solve
The relationship between releases and tags is not entirely clear in the UI, and users are not always aware creating a tag will automatically generate a release.
While convenient, generating releases from tags can cause a cascading effect of problems if the user does not realize the tag they just created already has a release associated to it (see insights).
Intended users
User experience goal
The user should easily understand how to create a Tag and associated Release at the same time
Proposal
- Remove the Release notes form field, as the preferred flow is to create them from the Releases page
🌀 See mockups in design management
Further details
Permissions and Security
Documentation
The documentation under Releases > Create a release in the tags page should be updated according to the changes introduced by issue.
Availability & Testing
Available Tier
- Free
What does success look like, and how can we measure that?
Users are successfully able to create a release from the tag creation page.
Success can be measured by observing user behavior on usability tests and/or UX scorecards.
What is the type of buyer?
Is this a cross-stage feature?
Links / references
Edited by Daniel Fosco