[Deploying Sakai] Ask the community: Your institution and Sakai bug reports

Stephen Marquard stephen.marquard at uct.ac.za
Mon Feb 2 06:24:57 PST 2015

Our Sakai does generate bug reports, which we parse into a separate database from which we generate summaries with click-through to detailed info. Code for the tools which do this is here:


We don't generally follow up with individual users, but typically investigate new bugs that crop up or appear to be affecting lots of users.


From: production-bounces at collab.sakaiproject.org [production-bounces at collab.sakaiproject.org] on behalf of Shawn Foster [sfoster9 at uwo.ca]
Sent: 30 January 2015 07:45 PM
To: sakai-user at collab.sakaiproject.org Server; production at collab.sakaiproject.org; sakai-dev at collab.sakaiproject.org Developers
Subject: [Deploying Sakai] Ask the community: Your institution and Sakai bug    reports

Some questions about Sakai bug reports:

1. Does your instance of Sakai generate bug reports?

2. How does your institution deal with bug reports generated from Sakai?

3. Does someone at your institution read/monitor the bug report email?

4. Do you follow up with your users who leave comments?

5. Do you follow up with your users who don't leave comments but who
cause a bug report?

Thanks for your opinions and anecdotes,

Shawn Foster
eLearning Technology Support and Application Development
Information Technology Services
Western University
London, Ontario, Canada
production mailing list
production at collab.sakaiproject.org

TO UNSUBSCRIBE: send email to production-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"


This e-mail is subject to the UCT ICT policies and e-mail disclaimer published on our website at http://www.uct.ac.za/about/policies/emaildisclaimer/ or obtainable from +27 21 650 9111. This e-mail is intended only for the person(s) to whom it is addressed. If the e-mail has reached you in error, please notify the author. If you are not the intended recipient of the e-mail you may not use, disclose, copy, redirect or print the content. If this e-mail is not related to the business of UCT it is sent by the sender in the sender's individual capacity.

More information about the production mailing list