Process step | Response | More informationWorkflow step | Customer response | Workflow step before | Workflow step after and response | Response |
---|---|---|---|---|---|---|
Added to backlog | Added to backlog | New | 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, | ||
Waiting for customer Request for change came in, however, process cannot begin until change request form has been completed. Reason:
| Customer change form | New | 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:
If you have any questions please do not hesitate to give me a call or email. Thank you, | 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, |
Idea backlog | 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 | 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 | 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 | 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. | |||||
Request deployment timeframe from customer | We have finished testing your requested change. When do you want us to deploy it to the production environment? Please let me know if you have any questions. | |||||
Awaiting deployment | 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. | |||||
Released to production | Your request for change has been deployed to production. You can review your request by clicking the following link. 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, |
Page Comparison
General
Content
Integrations