This article is to help decipher what is a change request versus a bug.
A change request is a formal proposal to alter something, typically in an organization or project. Change requests are often used to propose modifications to systems, processes, or products. They can be used to request new features, improvements, or fixes for issues or problems. Change requests typically outline the proposed change, the reasons for the change, and any potential impacts or implications of the change. They are often reviewed and approved by relevant parties before being implemented.
What is a bug?
A bug is an error, flaw, failure, or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways. Bugs can be caused by a variety of factors, such as coding errors, design flaws, or compatibility issues. They can have various impacts, ranging from minor annoyances to major security vulnerabilities. Bugs are typically fixed through the process of debugging, which involves identifying the cause of the bug and implementing a solution to fix it. In the context I provided earlier, a bug is an unexpected issue that needs to be fixed, as opposed to a change request, which is a proactive request to make a change.
What is the difference between a change request and a bug?
A change request is a request to alter something, typically in an organization or project. It can be used to request new features, improvements, or fixes for issues or problems. A bug, on the other hand, is an error, flaw, failure, or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways.
In general, a change request is a proactive request to make a change, while a bug is an unexpected issue that needs to be fixed. However, the distinction between a change request and a bug can sometimes be subjective, and there may be an overlap between the two. For example, a change request to add a new feature to a software program could be seen as a bug fix if the software is not functioning correctly without that feature.
Change requests:
- A change request is a formal proposal to alter something in an organization or project.
- Change requests can be used to request new features, improvements, or fixes for issues or problems.
- Change requests typically outline the proposed change, the reasons for the change, and any potential impacts or implications of the change.
- Change requests are often reviewed and approved by relevant parties before being implemented.
Bugs:
- A bug is an error, flaw, failure, or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways.
- Bugs can be caused by a variety of factors, such as coding errors, design flaws, or compatibility issues.
- Bugs can have various impacts, ranging from minor annoyances to major security vulnerabilities.
How are bugs fixed?
Bugs are typically fixed through the process of debugging, which involves identifying the cause of the bug and implementing a solution to fix it.
What do I do if I spot a bug?
You can submit bugs to your Project Manager, or you can submit a ticket via your customer portal. All tickets will be evaluated as to whether they are bugs or Change Requests. If a ticket is a Change Request, a change order will be produced and sent to the client before debugging or production.
How do I submit a Change Request?
Change requests can be submitted to your project manager or submitted via your customer portal. Requests submitted to a project manager will be turned into tickets. All change requests tickets will be sent for customer signoff before moving into production.
The status of all open Change Requests can be viewed in your customer portal.