Change Control Process

To ensure only verified code reaches production, CreativeTech implements a Change Control Process. All code destined for production undergoes a two-step internal approval process separate from QA. This happens after both QA and client approval.

This is not a QA process.⁠

⁠

Flex Frame (New or Edits), Custom Work, Paid Posts

Process

Create a JIRA ticket and assign Level 1 & Level 2 approvers (

refer to the provided list⁠

). Fig. 1

Follow the standard process for building, QA, and obtaining approvals. When everything is complete and ready for production, your card should be in the "QA External" column.

Once your ticket has final QA approval, move your card to the "Waiting for Approval" column. A confirmation dialog will appear. Fig 2.

Review the Approvers list and ensure it is correct. If unsure who the Level 1 & Level 2 approvers should be, consult

@Alysha Bindra⁠

@Michael Waskiewicz⁠

Note: Custom work and paid posts only require a Level 1 approver. In these cases, set both levels to the same person.

Click "Approve" to submit for approval.

Once approved by both approvers, you'll receive an email notification, and your card will automatically move to "Ready for Production."

Fig. 1

⁠

⁠

Fig. 2

⁠

Approver Instructions

When to Review:

You'll receive an email notification with a link to the JIRA ticket (APLD-####) and instructions for your review.

Reviewing the Ticket:

Click the link in the email to access the JIRA ticket.

Approving a Ticket:

In the "Awaiting Approval" section, choose "Approved by Approver #" (where # is your level). Fig. 3

A confirmation dialog will appear. Click the "Approved by Approver #" button to finalize your approval. Fig. 4

Rejecting a Ticket:

If you have concerns, contact the developer directly via Slack to discuss the issue and seek a quick resolution.

If the issue persists, you can return the ticket to QA for further work.

In the "Awaiting Approval" section, choose "In QA." This will notify the developer and move the ticket back to the QA stage.

Fig. 3

⁠

Fig. 4

⁠

Bugs

Currently, bugs are reported without formal change control. This may change in the future. For now, if a bug requires departmental oversight, submit it as a standard story in Jira. If you're unsure whether to create a bug or story, consult

@Alysha Bindra⁠

@Michael Waskiewicz⁠