Ideas
From Project Auriga
- Click to start timer
- Select or type account, project, task with flyout menus, perhaps?
- Hot list of Actionable items
- Mouseover for task deadlines
- Increase priorities as task approaches deadlines
- Maintenance checklist, sorted by date of last touch/priority of vulnerability
- Project templates make repeated projects a breeze, show average/last times for each task, sets deadlines for critical path, calculate current status/delivery date as scheduled
- Project templates are hierarchical outline form, useful as checklist
- Park a timer, add details later.
Drop-dead simple scheduling, views of team availability, individual availability, available to everyone
Personal time easy to schedule
Permissions system to show only what's necessary to who's allowed to see it:
- Hourly projects to customers
- Service contracts to customers
- Maintenance/fixed price show tasks completed, not time
Generic objects may be extended very easily with sane default behavior if unspecified. Provide table name, fields to insert/update, and auto load, save, and insert methods already do the heavy lifting.
Other standard object methods: default view, default chooser (to select parameters for default view), default editor, default report. Parent object choosers, child object lists
Containers: generally groups of objects on a tab that interact with each other. Main containers are for matching/synchronizing between databases, and scheduling tasks.
