Checklist - Change Data Request

A big difference between a code change and a data change is the task type is task. The update script is added to the Task, rather then tracked in Code and posted to a repository.

Deployment Requirements (put DB update, etc information here)

* Dev

* Test

* Production

Steps

* Confirm problem in localhost

* Fix problem

* Confirm fix in localhost

* status=CodeReview 

* Status=QA

* Send a database change request to have the test database updated.

* Test website - confirm problem repair

* Status=InUat

* Send to customer / ba for testing

* get delivery date

* Post announcement in @Change Management

* In Bitbucket, create a pull request (for example ‘times-454 - test → master’) (if multiple tickets are going to master, then specify the deployment Jira ticket number) (if othApps then add a code to help identity the application (for example 'othapps-594 - new hire - test → master')

* After approved, merge the test to master 

* On localhost, switch to master branch, do a pull

* build a new release using the master branch

* Status=Ready to Deploy

On the day of the rollout

* if there is a change to the production database, then create a ticket

At the time of the rollout

* Update Production Database

* Update Website

* Review and update Nutrition Label

* Update all tickets associated with this update. Status = closed

Copy / paste this into bottom portion description of task