We’ve developed a simple in-house project issues tool using Google Docs and Google Sites as we felt the issue list template didn’t give us the power of flexibility we needed. We created our tool in four simple steps. While it focuses on software development and bugs, this tool really can work for any kind of project. If you follow these steps, you’ll have your own in about 30 minutes.
- Create a Google site
- Create a spreadsheet.
- Create a form from that spreadsheet.
- Embed the form and the spreadsheet in the site.
Create the Google Site
Create a new site in Google Docs called ‘Bug Reporting Tool’. On the home page add any information about the project you need too. Then add two other pages, ‘Bug List’ and ‘Log a Bug’.
Create the Google Spreadsheet
This spreadsheet is going to be the powerhouse for the Google site. Create and save a new spreadsheet, then set the following column headers:
- Tester name
- Title
- Description
- Steps to reproduce
- Date
- Severity
- Date logged
- Date closed
- Notes
Create the Spreadsheet Form
Now create a form for that spreadsheet (Form Menu > Create Form). Set your sharing permissions on the spreadsheet. Developers should be able to edit it, and testers and others should only be able to view it. We’re going to set up the form now.
First edit the tester name field and check ‘make this a required question’. Click on done. Do exactly the same for the title field. Now, edit the description field and set the question type to ‘paragraph text’. Make it a required question and click on done. Do the same thing for the steps to reproduce field as you’ve done for description.
For the severity field we’ve set it’s question type to ‘choose from a list’, but ‘multiple choice’ will work just as well. It’s also a required question. Our four options on the list are:
- Critical – any bug that’s a show stopper. This means that the tester was prevented from using the software.
- Major – not a show stopper but still prevented the completion of a particular test although the tester could still use the software.
- Minor – Tester could complete a test but something went wrong along the way.
- Cosmetic – spelling mistakes, misaligned text fields and that sort of thing.
Date logged is a required text field. Unfortunately forms do not provide a calendar option, which is a pity. Date closed can be removed from the form. Notes is a ‘paragraph text’ question type but not a required question. If you like, set a theme for the form; we left it at the default. Click on save and the form is complete.
Embed the Google Spreadsheet and Form
Go back to your site, and edit the log a bug page, select ’spreadsheet form’ from the insert menu and select the form you’ve just created. Save the page.
Now edit the bug list page. Select spreadsheet from the insert menu to show the insert dialog, select the bug list spreadsheet and click on select. You’ll now be asked to choose some options. Choose view as list and click on save to embed the spreadsheet. Now save the page. Developers will be able to edit this spreadsheet embedded in the page, testers will only be able to view it. Developers can then update bugs as they fix them and testers etc will be able to view the bug list without editing it.
The sharing options are entirely up to you, obviously. For instance, your testing manager or senior testers may need to be able to edit the spreadsheet too or a customer may need access.
That’s it, job done.
If you have any queries/comments/questions please feel free to enter them below.
