Repository navigation
[STUD-507][Enhancement]: Update tooltip copy within the distribution user flow -- follow-up - #982
Merged
ITurres merged 2 commits intoFeb 26, 2026
Conversation
|
Visit the studio preview URL for this PR 🚀 : https://982.artist.preview.newm.io/ |
dmkirshon
approved these changes
Feb 26, 2026
dmkirshon
left a comment
Contributor
There was a problem hiding this comment.
Looks good, no blocking comments.
Comment on lines
+67
to
+85
| export const FIELDS_TOOLTIP_COPY_TEXT = { | ||
| instrumental: `Tracks without vocals or lyrics should be indicated as an instrumental. | ||
| Failure to accurately label the track could result in a declined distribution submission.`, | ||
|
|
||
| originalReleaseDate: `If your release has already been distributed on other platforms, | ||
| you may input the original release date here, but it's not required.`, | ||
|
|
||
| releaseCodeNumber: `A release code number is a unique code that identifies your release. | ||
| If you do not already have one, leave this field blank, | ||
| and a new release code number will be auto-generated for you.`, | ||
|
|
||
| releaseCodeType: `If you already have a release code, | ||
| select the code type here and enter the code in the next field. If not, | ||
| leave this field blank and a new release code will be auto-generated for you.`, | ||
|
|
||
| releaseDate: `When setting a release date, remember to factor in approval | ||
| from any collaborators and/or featured artists, as well as quality assurance checks, | ||
| which can take up to 15 days.`, | ||
| } as const; |
Contributor
There was a problem hiding this comment.
I could see this living in it's own file in common for copy text or some other organization pattern. It can wait till later in the end of phase 2 when other structure gets consolidated.
Member
Author
There was a problem hiding this comment.
Agree! I've updated STUD-560 to add this task as a cleanup.
ITurres
deleted the
STUD-507-Update-Release-Track-tooltip-copy--follow-up
branch
February 26, 2026 15:53
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request — Issue STUD-507
Overview
This PR centralizes and updates release/track tooltip copy in shared constants and replaces placeholder text in release details. It also aligns track copyright tooltip wording and links to the dedicated copyright FAQ anchor.
Clarification: for track-related fields in
AdvancedTrackDetailsthat need inline links, we can keep the JSX inline as-is, or consider a React-node constants map. Adding the copy to shared constants and splitting strings at render time is possible but is not the ideal approach.Files Summary
Total Changes: 3 files
Modified (3)
apps/studio/src/common/constants.tsapps/studio/src/pages/home/releases/release/ReleaseDetails.tsxapps/studio/src/pages/home/releases/release/tracks/AdvancedTrackDetails.tsxImpact
Testing
Related Issues
Dependencies
Additional Notes
--END--