Salesforce Sandbox Change Request and Release Notes
Write a change request and release note that users understand.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Write a change request and release note for a Salesforce change. The change: [CHANGE_DESCRIPTION]. Reason and benefit: [REASON]. Who is affected: [USERS]. Date: [DATE]. Testing done: [TESTING]. Change request: summary, reason, scope, fields and objects affected, dependencies (reports and integrations that use the changed field), risks with a risk rating and reasoning, test results, rollback, approvals, and a communication plan with dates. Pre-release checklist: tested in sandbox with realistic data, reviewed by an owner of the process, communication sent, support ready, rollback agreed. Fallback plan for the day: who decides to roll back and the trigger. Release note for users in two versions, a 30-word banner and a fuller note of under 150 words with screenshots described in words: what changed in plain words, what they must do differently on the first day, when, and where to get help. Add a training tip and a quick reference. Mark missing information [ADD] and the sandbox and deployment steps [VERIFY] because the exact process depends on how our org is managed.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.