The Bug Tracker app was developed to help organizations manage the recording and resolution of software bugs in custom software or custom configured SaaS applications. If you have software you are required to support and need to record and manage any issues that arise, then this template would be a great starting point. , then this template would be a great starting point.
The app allows you to organize and view bug by their auto-generated, unique Bug ID, priority and process stage. Bugs are assigned to a tech and either resolved, or rejected as a duplicate issue or one that can’t be replicated.
App Features
- Create bug records
- Track progress to resolution
- View and report on bug report progress
Bug Tracker Template Images |
|
Setting Up the Bug Tracker App
Please follow these steps to get the Bug Tracker app ready for use in your organization:
- Assign the appropriate people to the security roles within the application. Go to Lookup Application Setting > Edit App in the left side navigation, and once the app design screen appears, select Security > Roles and Users in the left side design navigation. Then select each of the applications roles (discussed below in App Design Details), and use the right side panel, that appears when you select a role, to set who should be in the role.
Using the Bug Tracker App
After discovering a new bug, enter its information into a Bug record. Then, click on the Submit Bug Report button at the top of the form. A software tech will then review the bug posting and either mark it as Accepted or contact the poster to get more details. After detailed investigation you may then mark the bug as Resolved or Not Reproducible.
App Design Details
- Bug: This form can be accessed by users from the ‘Dashboard’ page (instructions below), and there are several different views, each organized in a specific way. Beside the many Table views, this app has a Kanban view (click on one of the view names here to view the support page for editing and customizing these views).
-
Reader – Can view but not edit Bug records.
-
Reviewers – Can view but not edit Bug records, but can assign Bug records to developers.
-
Developers – Can view Bug records and edit them when they are assigned to development, plus review and mark as resolved accepted Bug records.
-
App Admin – Can view, edit & delete all records in the app.
All roles can create new Bug records. The record owner (creator of a Bug) can always view their Bugs, and can edit some fields when the record is at the In Review, Development and Request Details stages.
The workflow stages and the security access at each stage, are:
-
Draft – The App Admin role and the record owner can edit and delete the record.
-
Review – The Readers and Developers roles can view but not edit the record, the Reviewers role and the record owner can edit the record, and the App Admin role can edit and delete the record.
-
Assigned to Dev – The Readers and Reviewers roles can view but not edit the record, the Reviewers role and the record owner can edit the record, and App Admin role can edit and delete the record.
-
Resolved – All roles have only view access, except App Admin which can edit and delete the record.
-
Can’t Reproduce – All roles have only view access, except App Admin which can edit and delete the record.
-
Duplicate – All roles have only view access, except App Admin which can edit and delete the record.
-
Request Details – All roles have only view access, except the record owner who can edit the record, and App Admin which can edit and delete the record.
Workflow notifications are:
-
Draft stage – On submit, if the bug priority is ‘1. Critical’ or ‘2. High’ the Reviewer role is notified that there is a bug waiting review. The email template is called ‘New Bug Reported’.
-
Review stage – On Assign, the user identified in the Assign To field is notified that there is a bug needing resolution. The email template is called ‘New Bug Assigned’.
-
Assigned to Dev stage – On Update Bug Status, in most cases the requester is notified of the new status of the bug report. The email template is called ‘Update Bug Status’. If the update value is ‘Requested More Information’ the requester is notified of the new status of the bug report. The email template is called ‘Bug Needs Additional Information’.
-
Request Details stage – On Send Back to Dev, the user identified in the Assign To field is notified that additional information has been added to the bug report. The email template is called ‘Bug Info Updated’.
Updating the Bug Tracker App
Don’t forget, as well as being a fully functional app that’s ready to go, the Bug Tracker template app can also be a useful starting point for you to build from. If you want extra information tracked for your bugs, want additional views to sort the bugs in different ways, or want to track bugs for multiple applications, you can make those updates yourself. Our support site is a great place to get started learning how to make the changes you want.