Skip to content

Changes

Page history
Update WST Merge Request Process Overview authored by DAVID KUNKEL's avatar DAVID KUNKEL
Show whitespace changes
Inline Side-by-side
ADS/WST-Merge-Request-Process-Overview.md
View page @ 3cc4151a
......@@ -20,16 +20,13 @@ Drupal developers must follow the steps below when submitting a Merge Request (M
**Developer Peer Review steps:**
1. Upon completion of MR review `Steps to Test`, developer should ping BA for final testing in MR `Comments`.
2. **IMPORTANT** - Developer should then update the story in ES portal to change state from `Developer Peer Review` to `Testing` and update `Assignee` field to BA who will complete final review of MR.
1. Upon completion of MR review `Steps to Test`, developer should then update the story in ES portal to change state from `Developer Peer Review` to `Product Owner Review` and update `Assignee` field to Product Owner (Dennis Sutch) who will complete final review.
**BA Testing steps:**
**BA steps:**
1. **IMPORTANT** - BA should confirm a **Standard or Normal Change Request (CR)** has been added for the development work as needed. If no CR, BA should create one based on Acceptance Criteria and Technical Approach info on story in ES portal.
2. Upon completion of MR review `Steps to Test`, BA should ping main developer to indicate testing is complete in MR `Comments`.
2. **IMPORTANT** - BA should then update the story in ES portal to change state from `Testing` to `Product Owner Review` and update `Assignee` field to product owner (e.g. Dennis or Bill) who will complete final review and mark story as complete.
1. **IMPORTANT** - BA should determine if a **Standard or Normal Change Request (CR)** has been added for the development work as needed. If no CR, BA should create one based on Acceptance Criteria and Technical Approach info on story in ES portal.
**Merging Updates:**
1. **MOST IMPORTANT** - developer who completed peer review of MR should only merge the updates when they have confirmed a CR has been added for the update and approved (or scheduled).
1. **MOST IMPORTANT** - developer who completed peer review of MR should merge updates when they have confirmed a CR has been added for the update and approved (or scheduled).
2. Once approved CR has been confirmed, use `Merge` option on MR to merge changes to upstream master branch of project.
\ No newline at end of file