Thanks, Fredrik - but could I adapt them so that, instead of using them for bug tracking (don't need version control, etc.), they're just used for keeping track of simple tasks?
Fredrik Lundh wrote: > D wrote: > > > Hello, I apologize in advance for the vague description, but as of now > > I only have an idea of what I'd like to do, and need some guidance as > > to if it is feasible, and where to begin. Basically, I'd like to > > create a web-based "job jar", that users in my office can access in > > order to view, and "take ownership" of, misc. office tasks. One idea I > > had was that when users select a task (i.e. by selecting a check box > > and clicking an UPDATE button), tasks are automatically put in an In > > Progress list (which identifies the task and the user who took > > ownership of it) - then, when the action is complete, the user updates > > it again which puts it in a Completed list (again, with the task > > description and the user who completed it). However, only certain > > users should be able to add and modify task descriptions. > > why not use an issue tracker? > > http://roundup.sourceforge.net/ > http://trac.edgewall.org/ > https://launchpad.net/ > > (etc) > > </F> -- http://mail.python.org/mailman/listinfo/python-list