[OPEN-ILS-GENERAL] Bug Tracking and Enhancment Requests
We are beginning to look at software to track bug reports within our consortium and enhancement requests for potential future development by our member libraries. We are looking for something that would be fairly user friendly for our member libraries and allow us to easily group requests and report back to member libraries what actions might have been taken on the requests. I appreciate whatever suggestions you might have. We do run a Drupal site on wamp so if it can integrate with Drupal (with an eye for the ability to run on future versions of Drupal would be helpful.) -- Tim Spindler Manager of Library Applications tspind...@cwmars.org 508-755-3323 x20 IM: tjspindler (AOL, meebo, google wave) C/W MARS, Inc. 67 Millbrook St, Suite 201 Worcester, MA 01606 http://www.cwmars.org *P** Go Green - **Save a tree! Please don't print this e-mail unless it's really necessary.*
Re: [OPEN-ILS-GENERAL] Bug Tracking and Enhancment Requests
Hi, On 09/16/2011 10:50 AM, Tim Spindler wrote: We are beginning to look at software to track bug reports within our consortium and enhancement requests for potential future development by our member libraries. We are looking for something that would be fairly user friendly for our member libraries and allow us to easily group requests and report back to member libraries what actions might have been taken on the requests. I appreciate whatever suggestions you might have. We do run a Drupal site on wamp so if it can integrate with Drupal (with an eye for the ability to run on future versions of Drupal would be helpful.) I've never seen a perfect bug tracker, but several ones that I know have been used with various degrees of success include: [1] Bugzilla. This might score a little low on the user friendly scale, although recent versions have had the benefit of some formal usability testing. Of particular note is the existence of the Launchpad-Bugzilla plugin. I haven't used it myself, but being able to connect bug reports in your tracker to LP bugs seems like it would be useful and would help avoid atomizing enhancement requests. Other F/OSS trackers that can integrate with LP are Trac and Mantis. [2] RT (http://bestpractical.com/rt/) I believe this is being used successfully by at least one other Evergreen consortium. [2] HelpSpot This is proprietary, unfortunately, but it's what Equinox and at least one other Evergreen consortium uses for support incident tracking. Regards, Galen -- Galen Charlton Director of Support and Implementation Equinox Software, Inc. / Your Library's Guide to Open Source email: g...@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web:http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org http://evergreen-ils.org
Re: [OPEN-ILS-GENERAL] Bug Tracking and Enhancment Requests
On Friday, September 16, 2011 12:28:21 PM Galen Charlton wrote: [2] RT (http://bestpractical.com/rt/) I believe this is being used successfully by at least one other Evergreen consortium. We use RT here at PLS. I like it, it lets us setup permissions, add requestors to tickets, merge tickets, have automatic responses when something happens to a ticket, automatically BCC people when something happens to a ticket (ie: there are 4-5 people who get BCCed with any updates are made to a ticket in the Evergreen queue), mark tickets as dependent on other tickets, depended on by other tickets, mark tickets as parents or children of other tickets, etc. We have it setup with our mail system, so when you send an email, it will automatically open a ticket for the sender in the correct queue. Also (unlike some ticketing systems) when you reply via email from the ticket, the reply goes into the ticket. You can either reply to the requestor or you can add a comment (added to the ticket, but not sent to the requestor) via email. Downsides: The web UI on our version is clunky (but the libraries never use it, they just use email to interact with RT), and our antiquated version needs some tweaks to the config files from time to time. See: http://issues.bestpractical.com/Dashboards/1408/RT?user=guest;pass=guest for the interface of a current version. Aaron Z Jr. Systems Administrator Pioneer Library System 2557 State Rt. 21 Canandaigua, New York 14424 Phone: (585) 394-8260
Re: [OPEN-ILS-GENERAL] Bug Tracking and Enhancment Requests
We use Request Tracker along with the ExternalAuth plugin to authenticate against our Drupal site. We are happy with it, but it isn't perfect. Contact me off list if you'd like to discuss. Regards, Justin Hopkins Coordinator, IT Web Services MOBIUS Consortium Office c: 573-808-2309 --sent from a mobile device-- On Sep 16, 2011, at 11:29 AM, Galen Charlton g...@esilibrary.com wrote: Hi, On 09/16/2011 10:50 AM, Tim Spindler wrote: We are beginning to look at software to track bug reports within our consortium and enhancement requests for potential future development by our member libraries. We are looking for something that would be fairly user friendly for our member libraries and allow us to easily group requests and report back to member libraries what actions might have been taken on the requests. I appreciate whatever suggestions you might have. We do run a Drupal site on wamp so if it can integrate with Drupal (with an eye for the ability to run on future versions of Drupal would be helpful.) I've never seen a perfect bug tracker, but several ones that I know have been used with various degrees of success include: [1] Bugzilla. This might score a little low on the user friendly scale, although recent versions have had the benefit of some formal usability testing. Of particular note is the existence of the Launchpad-Bugzilla plugin. I haven't used it myself, but being able to connect bug reports in your tracker to LP bugs seems like it would be useful and would help avoid atomizing enhancement requests. Other F/OSS trackers that can integrate with LP are Trac and Mantis. [2] RT (http://bestpractical.com/rt/) I believe this is being used successfully by at least one other Evergreen consortium. [2] HelpSpot This is proprietary, unfortunately, but it's what Equinox and at least one other Evergreen consortium uses for support incident tracking. Regards, Galen -- Galen Charlton Director of Support and Implementation Equinox Software, Inc. / Your Library's Guide to Open Source email: g...@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web:http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org http://evergreen-ils.org
