Change management
Kentucky uses its built-in task function to handle any wanted / needed changes to either Kentucky itself or a specific implementation. The super user for the specific implementation is responsible for creating and verifying change requests.
Change management process
-
The super user creates a new task.
-
The Kentucky development team analyzes and prioritizes the task.
-
The Kentucky development team solves the task and deploys the changes to the QA environment.
-
The super user verifies the changes in the QA environment and either approves or gives feedback.
-
The Kentucky developmen team deploys the changes to production (if approved).
During this process the status of the task will be changed to reflect its current position in the process.
Task statuses
- Not started
-
All tasks starts in this status. It is the initial registered status which all tasks get after a superuser creates them.
- On Hold
-
This status is used if the task needs to be paused for some reason.
- In Progress
-
When the task reaches this point it means someone, developer or other support personnel started working on the task.
- Review
-
When the task reaches this state it means the support personnel are ready with the change and has deployed it to a QA (Quality Assurance) environment.
- Completed
-
When the task is completed, approved and released in production.