Skip to end of banner
Go to start of banner

Customer responses to change request process

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Workflow step

Workflow step after and response

Customer response

The change request has been received; however, the process cannot commence until the change request form is fully completed.

Reason:

  • The request was not submitted through the appropriate channel.

Once a customer submits their response, the subsequent step in the workflow will be labeled as ‘Added to backlog.’

Thank you for your submission for a request for change. I attached a form to your ticket that will allow us to process your request more efficiently. This will also help our department get a better idea on expected outcomes and priority. Below is a list of steps to submit the change request form.

Steps to complete:

  • Click: https://ssdmo.atlassian.net/servicedesk/customer/portal/4/$issueKey$

  • Scroll to the bottom of the screen to section: 'DevOps - Change request'.

  • Click the blue button 'Edit'.

  • Fill out all the required fields marked with a red asterisk.

  • Click the blue button 'Submit'.

  • Enter a comment in the 'Add a comment' field that says you have completed the form.

  • Click button 'Save'.

If you have any questions please do not hesitate to give me a call or email.

Thank you,

Added to backlog

  • The change request has been successfully added to the Technology Services backlog and will be assessed according to its priority level.

Added to backlog

Thank you for your submission. We will add this request to the backlog and get back to you when we have evaluated the request and have developed a timeline for implementation and delivery.

Note: if you feel this issue needs to be a higher priority, please don't hesitate to respond to this ticket.

Thank you,

A change request was submitted; however, it has been categorized as an idea. It's important to note that ideas may not always be executed, as they often encompass a wide range of possibilities or may not align with the District's current priorities.

Moved to ‘Idea workflow’.

Thank you for your idea submission. Technology Services reviews submitted ideas/suggestions on a regular basis and your idea will be considered inline with District priorities. We will add this request to the backlog and get back to you if it is selected for implementation.

Note: if you feel this issue needs to be a higher priority, please don't hesitate to respond to this ticket.

Respectfully,

Evaluating solution

  • Gathering requirements, creating a Proof-of-Concept (POC), and defining the project scope are essential steps in determining whether the proposed changes can be effectively implemented by the change initiator.

  • Once the requirements are sufficiently defined, the change coordinator will have all the necessary information to develop a comprehensive plan and explore various options.

We are currently assessing your request. We will keep you informed regarding the scheduling of the implementation as soon as we have more information to share on this ticket.

Feel free to reach out if you have any questions.

Thank you,

Assigned release

  • The release/version has been confirmed; however, work has yet to commence and a resource must still be allocated.

Your request has been assigned to a release and is scheduled for processing. However, a resource has not yet been allocated. We will provide further updates on the progress of your request as soon as more information becomes available.

Feel free to reach out if you have any questions.

Implementing

  • Development, testing, and documentation of request is being completed.

We are currently in the process of implementing your request. When we have any additional information related to the delivery of your request we will update this ticket.

Please let me know if you have any questions.

Development complete and deployment timeframe communicated to customer

  • The request has been successfully fulfilled.

  • Date to review deployment with CAB.

  • Involved with the deployment workflow.

We have successfully completed testing the changes you requested. The next deployment window is set for: [DATE AND TIME].

If the proposed timing is not convenient, please refer to the change calendar to select the next available deployment window that fits your schedule, and respond to this ticket accordingly.

Next step: Reviewing deployment date with Change Advisory Board (CAB) on: [DATE]

Please let me know if you have any questions.

Deployment scheduled (New status)

  • Deployment request has been approved by the CAB and a date has been set.

  • Involved with the deployment workflow.

  • May been involved with StatusPage workflow

Your change request has been approved for deployment. The deployment is scheduled for: <ADD DATE> at: <ADD TIME>.

Please let me know if you have any questions.

Awaiting deployment approval or Needs approval (Status name change)

  • Timeframe of deployment has been confirmed by customer. However, deployment must be approved by the CAB.

  • Involved with the deployment workflow.

Released (New status)

  • Change request has been successfully deployed to the production environment.

  • Involved with the deployment workflow.

Your request for change has been deployed to production. You can review your request by clicking the following link.
https://ssdmo.atlassian.net/servicedesk/customer/portal/4/$issueKey$

Could you please verify that your request has been satisfied so we can resolve your ticket?

Thank you,

Priority change

Regrettably, we have been dealing with other more urgent matters that have diverted our focus from your request. However, rest assured that your ticket is in line for processing. You will be notified as soon as work recommences on your request.

Thank you for your patience,

  • No labels