11
« on: March 06, 2009, 11:37:49 pm »
I know I am not asking for anything new. I have seen one of the discussions on this topic. The suggestion given to the requester was to use OpenGoo as the Bug reporting tool. So all the user can do is to create a task as a Bug and get it treated as a normal task OR the user can create a Sub workspace for Bug reporting and ask the Tester to log Bugs in that Sub-Workspace as a task.
But at the end of the day, how can one come to know by just seeing a Task that its a Reported Bug or a normal task?
From the usability point of view I think there should be a separate way to know whether a particular task is a bug or a work request.
The easiest way out can be to just give an option - Report Bug.
When a user opens the "Report Bug" page, he would be presented with the same page as the one used in creating a task. Only difference will be that there will be a classification of this Task as a "Bug". Rest things like priority, assignee, timeline etc etc will remain same as that of a normal Task. Thus with minimal changes OpenGoo will have Bug Reporting functionality too.
Since we are classifying tasks as Task and Bugs so we will have to have an entry for "Pending Bugs" on the dashboard. User shall also have an option to generate the bug report.
Once my programmers are free from billable works I will see that they put in some time in Open Goo and customize it for Bug reporting. Meanwhile if OpenGoo team does that, it will be wonderful. I have tried to peep into OpenGoo code...its very complex. I could not find any documentation and much time in my hand, because of which could not proceed further.
Regards,
Nitin