Log once, read anytime - Why logging issues is important
Although this sounds obvious it's still something we don't always do and the only realreason is sheer lazyness. The only real disadvantage is that it takes a few minutes to do but the benefits completely out weigh this.
Where I work currently didn't have a method of storing customer issues. This resulted in all the developers keeping emails all over the shop. What this means is that the same developers could all find the same issue, all resolve the issue and all store what the issue is and how to resolve the issue without telling any of the other developers unless the developer happens to ask someone.
I have personally fixed an issue myself and then couldn't find the email with the answer on. Even today I had an issue but managed to find the email with the answers and put it into bugzilla.
Bugzilla for those who haven't heard of it, is a nifty open source for storing and searching your bugs
http://www.bugzilla.org/
The main benefit of logging your bugs into a database is the fact that you and the othe members of your team can search the database and find details on what the bug is, how to recreate it and most importantly how it has been fixed or a workaround. This way the solution is safe from data hiding or people just forgetting how to resolve a bug. You can even see who delt with the bug before and ask them about it.
Having a bug database is even more useful to people who have just joined the company and don't have a clue about certain parts of the system, let alone fixing them. They can search the bug database, read the answer and then get back to the customer as if they have just fixed the problem themselves.
Having a bug database also allows the development team to see what bugs are currently outstanding and need to be fixed. Sometimes people are changing a certain piece of code for another reason and whilst they are there they can fix another bug. Sometimes people need a small bit of work before they start another project, boom they can look in the bugzilla and find something to get their teeth into.
It's also useful to see what customers have raised what issue's and how many they currently have waiting.
Lastly and quite importantly it creates a system where everyone knows where to look for information about bugs, everyone logs bugs in the same place and all the information is stored in central location. The knowledged is shared.
So remember next time you have got an issue which you have solved, put it in the bug database one day you will go back there and give yourself a good pat on the back for doing it
Where I work currently didn't have a method of storing customer issues. This resulted in all the developers keeping emails all over the shop. What this means is that the same developers could all find the same issue, all resolve the issue and all store what the issue is and how to resolve the issue without telling any of the other developers unless the developer happens to ask someone.
I have personally fixed an issue myself and then couldn't find the email with the answer on. Even today I had an issue but managed to find the email with the answers and put it into bugzilla.
Bugzilla for those who haven't heard of it, is a nifty open source for storing and searching your bugs
http://www.bugzilla.org/
The main benefit of logging your bugs into a database is the fact that you and the othe members of your team can search the database and find details on what the bug is, how to recreate it and most importantly how it has been fixed or a workaround. This way the solution is safe from data hiding or people just forgetting how to resolve a bug. You can even see who delt with the bug before and ask them about it.
Having a bug database is even more useful to people who have just joined the company and don't have a clue about certain parts of the system, let alone fixing them. They can search the bug database, read the answer and then get back to the customer as if they have just fixed the problem themselves.
Having a bug database also allows the development team to see what bugs are currently outstanding and need to be fixed. Sometimes people are changing a certain piece of code for another reason and whilst they are there they can fix another bug. Sometimes people need a small bit of work before they start another project, boom they can look in the bugzilla and find something to get their teeth into.
It's also useful to see what customers have raised what issue's and how many they currently have waiting.
Lastly and quite importantly it creates a system where everyone knows where to look for information about bugs, everyone logs bugs in the same place and all the information is stored in central location. The knowledged is shared.
So remember next time you have got an issue which you have solved, put it in the bug database one day you will go back there and give yourself a good pat on the back for doing it
posted by The Hosk at
12:59 pm
0 Comments:
Post a Comment
<< Home