...
The pull request title should always be formatted as SPR-123 Story Title. The description should include:
A link to the storyA brief description of the changes made
DOD checklist (part of template)
List of test cases to review
Release notes
CS-facing description of what changed
Before/after screenshots/recording if applicable depending on the nature of the story
A link to the story
Acceptance criteria
| Tip |
|---|
Changes meet all criteria specified in the Jira issue and also any related Confluence documents associated with the epic where applicable. |
...
This documentation space is a good opportunity to explain implementation details and reasoning/limitations to provide additional context for support teams.
Release notes and documentation can be updated at any point during development, and should be fully completed prior to merging the pull request.