Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Pre-Build

  • Verify that all

...

  • JIRAs owned by you (you are the assignee) reflect the proper values for selection by the automated tool

...

Jiras going to PRD should always have a fix version assigned that corresponds to the next planned release.
  • Fix Version must = next release
  • Jira should be Resolved
  • Customization status must be “User Accepted”
  • UAT Status must be “Passed”
Jiras going to UAT
  • Jira must be Unresolved
  • Jira must be “In Progress”
  • Customization status must be “Unit Testing Complete”
  • Are there external file dependencies for deplyment/build?  If so set the checkbox & paste svn link to files in JIRA comment, along with instructions & dependencies for execution fo the CM.

Post-Build (any environment)

  • Verify that the changes and all their dependencies have arrived in the target environment.
  • Verify that any required SQL scripts have been executed without error.
  • Verify

...

  • the JIRA status field values

...

Post deplyment - PRD – please make sure you take the following actions
  • Verify that changes have arrived and are complete (may need to work with requestor)
  • Set status to “Closed”
  • Verify that customization status is set to “Deployed to PRD”

...

  • .

Post deployment - UAT

  • Perform a unit test to verify that the changes and all dependencies are in place.Verify that the customization status is “Deployed to UAT”
  • Assign the Jira to the requestor providing comment informing them that the change is in UAT and ready for their validation. Also tell them the date of the next scheduled PRD build so they know what their target completion for testing is.

Post deplyment - PRD

  • Verify that changes have arrived and are complete (may need to work with requestor)

Workflows

  Issue Types : Bug, Improvement, New Feature - will follow a complete workflow involving requirements signoff, QA and UAT testing.

  Issue Types : Data, Process, Task, Subtask, Other - will follow a simplified workflow that does not involve formal requirements signoff, QA or UAT testing.

  Each step in the workflow is designed for a specific user role.  Current users are defined in the User Roles page.