Client Configuration Change Workflow Statuses
- Chadd Marks
Workflow Status | Description | Client Action? |
|---|---|---|
New | Ticket has been created. | No |
Researching Change | Determining ask of request. | No |
Client Success Review | Client Success is reviewing the request. | No |
More Information Needed | Additional information is needed to complete the request. | Yes - Provide the information requested on the ticket. |
Client Response Received | Client has responded on the ticket. | No |
Pending Product Change | Ticket is pending a product story to complete the request. | No |
In Development Backlog | Ticket is assigned to the support backlog and will be prioritized based on urgency. | No |
Ready to Work | Ticket is ready to be pulled into a sprint for development work. | No |
Ready for Non Code Change | Ticket is ready to be pulled into a sprint for non development work (config app). | No |
In Active Sprint | Ticket is assigned to an active sprint and will be worked. | No |
Client Verification | Non development ticket is ready for client UAT. | Yes - Client conducts UAT and leaves a comment on the ticket either approving or rejecting the change. |
Ready to Release | Change is ready to be deployed to production. | No |
Released to Staging | Code has been deployed to the clients staging environment. | Yes - Client conducts UAT and leaves a comment on the ticket either approving or rejecting the change. |
Released to Production | Code/Change has been deployed to clients production environment. | No |
Completed No Code Change | Request is working as designed or no longer required. | No |
Withdrawn | Request is no longer valid or required. | No |