One of the things I want to add is a way to send tickets, control, report and analize computer and network problems reported by the users to the technical department.
I started to develop all I need to acomplish it.
Is anybody else interested in such feature? Suggestions will be welcome.
We're starting to work on getting a ticketing/project management system (looking at tutos or phpprojekt) integrated, so I could have single interface to host training materials, project management/time tracking, trouble tickets, and FAQ We currently use Double Choco Latte connected with Mindmeld for the FAQ. Mindmeld is an incredibly powerful tool, but I'm not as happy with DCL and so we're looking at other project management/ticketing systems.
We'll be starting this project in January if you are interested in collaborating or sharing ideas.
depending on what are your requirements you might be interested in HOT (hot open tickets), which is an open source php solution of a sourceforge project.
Date: 11:31 PM 22-Jul-2003 I'm not sure if this can help, but:
seems to be a good workgroup software.
We thought some forms of courses might benefit from an integrated project management tool as well.
It would be like a forum post that can be custom tagged per instance (like the custom rating system -- create tracking stages just as you create rating criteria) as a feature request, bug, etc.. Then as the bug is tested, resolved, etc. it is tagged and flagged as such. Each new post would be like adding a new discussion, so you have a familiar forum (with attachments) built into every tracker request (along with subscriptions, etc.).
But you would want to create a new view/sorting interface that would show all of the various stages of the tagging.
While this would fully integrate a tracker within Moodle, it would also provide flexibility for teachers to track anything. Instead of tracking bugs, they might track projects, they might track independent reading, to dos, etc.. It would be HIGHLY flexible. (It would even more flexible if these integrated with the calendar and if some of the tracker instances were private to the teacher/student).
I wish your excellent team might consider this one. While bringing in systems from the outside often work, they never feel "moodle-y" enough for my taste.
Yes ... I guess one of the important things is to maintain the moodle feeling.
Also, such "external" software is too complex for the current needs.
By the way, should tickets be assigned to somebody for solving? I mean, everybody may post things in the forum, but, in this particular case this feature should be avoided. Tickets should be assigned to a specific person that must solve it. We need also a ticket numbering system to refer to a post.
In the current bugtracker (moodle.org/bugs), everyone can contribute/subscribe to a bug, but the bug is still assigned to a single person (maybe the teacher that creates the individual tracker instance could create a list of people who could be assigned the task).
Wouldn't the postid serve as a ticket #?
I'm not sure about the severity issue. Who decides it? Could the severity be calculated by everyone using the built in rating system?
Severity rating.... (drop down) = use existing rating system with private and public responses.
Assign task... (drop down) = draw from a list of individuals created by teacher (use existing subscription interface to create list).
I only wish that certain instances of the tracker (I see them spread throughout the course) could be designated for student only, or teacher/student only. For example, a student might want to create a todo list (that is reflected in the calendar); or a teacher might want to create a skills tracker that plots a student's progress with certain concepts or skill (i.e. reading comprehension, involvement in discussion, ability to use punctuation correctly, etc.).
I guess the ticket number could not be the post ID because it should be correlative, should't it?