Simple Web Based task/job/todo Manager?

[ajt]

A colleague at work needs a simple job managment tool. He wants a dead simple web interface, and the ability to create a job/task, edit it, and search for it, and not much else.

Something like RT is far too complex, I'm looking for something much simpler. My options are to find something, or build a simple web front end round SQLite (or similar) and TT2.

I've done a quick search round CPAN, and here, but most references to task/job are to CPU process, and ToDos refer to things to do in a module...

I'd naturally prefer a Perl solution, just so I have a better chance at understanding it, but it must run on Apache/Linux and allow my colleage to do fancy eye-candy messing with the front end.

I'm quite happy to build something custom for him, but If there is something that can provide the job managment already I'd be very happy to use it first rather than build by own wheel, or use it as the wheel for my own small application.

Any ideas or suggestions?

[Corion]

As long as you're not aiming for anything complicated, Maypole as a frontend to a database is enough. It'll give you a view of the rows of some tables, and (clickable) links between the tables. Adding more functionality to it is possible, but if you require actual workflow, I'd go with RT instead of baking my own solution.

[techgirl]

Why rebuild? Basecamp is the best thing I've ever used -- although not written in Perl. It has a limited free version as well... I love it.

[Taulmarill]

imho Maypole is capable of some more complex things, as long as the db-table->method logic make sense.
for all the other complex tasks i would assume you wait for the next incarnation of Maypole, which should be mutch more versatile.

[Corion]

I'm not saying that Maypole is not capable of complex things, but there are quickly diminishing returns once you stack more complexity on Maypole. Maypole gives you a quick start if your application fits well into the Maypole model of things. It makes no sense to use Maypole instead of writing your own framework if you have to either bend your requirements to make them fit to Maypole or if you have to bend Maypole to have it fit your requirements.

And as there already is a good ticketing/tracking solution, I would not waste the time by writing and expanding my own solution but rather use the existing solution.

[rob_au]

For a similar task, we (at work) employed Bugzilla (http://www.bugzilla.org/) without issue.

[Fletch]

If you don't need much fancy functionality you might could wrangle something like Kwiki or Blosxom into behaving the way you want. I set up the later to track project status and todo items at work with a few custom plugins and a convenience script that hides some of the paths involved (i.e. projects are categories and you say you want to add a new status entry for project foo; the wrapper then starts:
$EDITOR /bloxsomroot/foo/foo_status_datestamp.txt for you).

[stvn]

If you go about building your own, you might want to look into Workflow. I haven't used it myself, but I have read over the docs and it seems pretty interesting.

It even seems to come with a small job ticketing system as an example usage, it might be a good starting point for you.

[elusion]

It's not written in Perl, but I've used Tasks before. It's written in PHP, so it's not very hard to set up. There a couple different versions; I've used the free one.

[YuckFoo]

If you really want simple and want to roll your own, Notepad.pl may give you some ideas.

YuckFoo

[csuhockey3]

I second Notepad.pl, although I don't use it anymore. I had a manager a while back use that to teach me more perl (more CGI in particular). It was a great starting place that allows you to 'build your own' -- if I can find that old code, I'll post.