Forum OpenACS Q&A: New Features for Bug Tracker
The features are
- Create a new bug/ticket by email
- Allow upload of related files to a bug/ticket
- Add bulk actions, to reassign,resolve, or close multiple bugs/tickets
- Add email summary, this allows sending a email with a listing of tickets
These features are available in CVS HEAD now.
Additional work that is planned includes
- commenting/editing tickets by email
- configurable workflows/permissions to allow different types of access
- speeding up bug tracker
- adding AJAX enhanced UI for certain operations
Sounds great. Would it be possible to use this version on openacs.org?
I will see if I can update it soon.
A merge with openacs.org bt would be nice too, so we can finally have a full-text search in bug tracker.
Also, the fix for version field should be optional via parameter in case you want a support ticket system and not a bug tracker.
There's also a missing message key in workflow for the comments:
MESSAGE KEY MISSING: 'workflow.lt_creation_date_pretty_'
Currently, the openacs.org bt uses the search package and tsearch2 but does not narrow the search to the bt instance specified in p_id. It also doesn't provide meaningful descriptions.
A more involved enhancement would be to add text and/or drop down filters to each column of a list template. This would be an excellent addition to list builder in general. Currently searching for arbitrary data inside a list template is very difficult unless your data matches one of the filters.
What do people think? I'd like to try something like this, but I'd need some assistance from a developer with a bit more experience and commit rights.
I have done a per-column filter UI for listbuilder that is not quite ready to be ditributed.
Additionally I was wondering if you want to up the version number. I think oacs-5-4 is at 1.5.x while head is at 1.4d4, so my installation got confused when I tried to upgrade.
I have never noticed any problem with bug-tracker notifications, I haven't made any changes to that at all in relation to this new work.
On my own instance of bug-tracker, they don't work at all and I am in the process of debugging workflow why that is the case, but with your E-Mail summary function it is even better as I can shove it under the developers nose whenever I want to, not when he thinks he likes to receive notifications.
Thanks for that information. I can't understand why it doesn't work, and it might have something to do with workflow since that is what actually triggers the notifications.
Can anyone with bt from HEAD installed confirm this?