Summary

• Overview of changes
• A link to the Jira ticket for quick reference

• Closes #XXXX

How to test

1. Instructions on how to test the changes in this PR.

Checklist

• Prefixed the PR title with the Jira ticket number as [CMSDS-####] Title or [NO-TICKET] if this is unticketed work.
• Selected appropriate Type (only one) label for this PR, if it is a breaking change, label should only be Type: Breaking
• Selected appropriate Impacts, multiple can be selected.
• Selected appropriate release milestone

If this is a change to design:

• If visual regression image references have been changed, design MUST be assigned to review. In this instance, designer approval is a requirement before the PR can be merged.

If this is a change to code:

• Created or updated unit tests to cover any new or modified code
• Verified that running both npm run test:unit and npm run test:browser:all were each successful
• If necessary, updated unit-test snapshots (npm run test:unit:update) and browser-test snapshots (npm run test:browser:all:update)

If this is a change to documentation/content:

• Checked for spelling and grammatical errors
• Communicate the assigned milestone/release date with Design so they can communicate appropriately