Local Mail server

more details about the task please.

-- the best things in life are free --- so as myself

If I understand this correctly, I have a similar problem in my previous work. There were regular scheduled tasks (about 60 task/day) and variant requests per day. Tasks and Requests should be assigned to members of the team for work balance.

They were working through a Spread Sheet that list all regular tasks however requests were totaly handled through emails. The Spread Sheet was copied every day from a template to reflect the date in its name and then filled by team members to know if task is done or not.

I didn't like that way and I guess all of you too. So I make a small application with back-end database to make tasks/requests managements easier, distributed equally between team members and can be monitored also from any of them.

I called it "Work Order" where everyday, we have a new Work Order with new tasks/requests scheduled for that day. If new request received, it should be registered in the system. Every task/request is assigned to a team member. When he/she finish it, he simply mark it "Closed". If he had problem operating the task, he'll mark it "On Hold" and then he had to issue a problem reporting using the same system to inform others that he is facing a problem operating that task.

That system was integrated with Mail Server to send a proper notifications to team members and even SMSs when task time is exceeded.

The back-end database was very useful extracting reports of tasks/requests/problem that's operated in any day.

Unfortunately, I didn't built that solution on FOSS solutions. But if you think it'll be of benefit to you and others, I'll be happy to port it to be open source through EGLUG.