K2 Defect Tracking Accelerator
The Defect Tracking process is built to capture defects in applications and ensure that these are addressed. The application is designed to be generic and may need some tweaks in order to comply with specific implementations. The request form, completed by a user that interacts with the system (typically developers and testers), captures the necessary details about the defect, then starts a workflow that will route the request to relevant employee(s) in order to get resolved.
If the defect is of a lower priority, it is sent to the administrator of the server and application. If it is of a sufficiently high priority, it gets sent directly to the Developer for fixing. If the administrators approves the defect, it will also get sent to the Developer.
Once the developer has a resolution for the defect, it gets sent to the originator to validate the fix. If the defect has not been addressed, it will go back to the developer. Both the administrator and the developer can also send the item back to the originator to resolve queries about the defect.
Submitter’s Confirmation of Resolution
There are a number of lists that can be configured for this accelerator.
- Applications, Servers, Priorities and Resolution Types
- Participant Configuration – Administrator by server/application, developer by server/application
Home screen for users
Users are able to see requests they submitted and requests that are assigned to them for approval.
How does this help you?
If you are looking to use this as a baseline for building an enterprise strength Defect Tracking Solution, here are a few things we recommend you do:
- Move from Smartbox SmartObjects to your own SQL database.
- Configure various administrative lists
- Remove originator from the destination rules. We believe this is done primarily for ease of testing and demonstration.