A quick summary of our experience with Bugnet.
We are a small (6 people) development team developing a Windows desktop application in Delphi. We have used “Software With Brains: for many years and this was part of our day-to-day task management.
Earlier this year we started with Bugnet and converted ~6000 SWB items into the Bugnet database. I used two Bugnet projects, one for current items and on for closed items. The closed items were retained as there are often comments
in the code that references the bug #.
Conversion was relatively straight forward and it was a real bonus that I could retain the original Ids.
One of the major attractions of Bugnet was the Summary page. In practice this has been a disappointment. The limitation is that each group of users has there own view on which items are Active (ie not closed).
For example developers need to know which items are ‘in development’ and do not want to see items that are further down the workflow.
- Search tool does not handle NULLs very well.
- Bulk edit fails (some issue with credentials).
- Lack of defaults for new issues
- Lack of data validation (‘required’ fields based on status, would be a start. Sub-lists against each status would be better).
In order to provide the team members with a view of their outstanding work, I have put together a desktop app. that uses a local SQL connection and displays issue data in a Developer Express grid. The in-built features of the
grid control provide filtering and grouping and provides 90% of the functionality we required. In addition to the data access, added code to retain the layout and view selection.
This solution works well for us and I would be happy to make it available. I don’t know if these (or similar) tools exist in the Web space but you might consider this as a prototype for a Web-based implementation.
CRS Software Ltd