Johan Bernhardsson schrieb: > Notes on OpenPSA. > ================= > Some notes on OpenPSA collected from conversations with bergie and flack. > > **Projects:** > - On creation of a project a project number should be created much like > invoice numbers. This will ease registration of incoming invoices and > expences. > - The id should be shown everywhere to easy tracking of the project. A > project name is handy but not to everyone. (For example if you have three new > server sales projects at the same time.) > - Tasks should be linked to a customer aswell. > All projects should be linked to a customer. Regardless if we have an > agreement from sales or not.
There is already a mandatory customer field when you create a project, but from a database point of view, this is not very elegant, since it introduces redundancy. F.x. if a project is linked to a salesproject, you'd need to make sure that the salesproject customer and the project customer match on each update. Salesprojects also have this autogenerated project number you mention, so I'm wondering if it wouldn't be better to merge salesproject and project into one database table. Or at least to take out the rendundancies between the two. > > **Sales:** > - When deliverables in a sale should be grouped together. When a sale is > accepted by a customer, that sale should be transformed to a project with a > project id. So when we invoice we will only have one invoice regardless on > how many deliverables we have. And we should be able to select only some > deliverables for one sale. (The client takes the server and installation but > not the five workstations for example.) > - Next event for a sale should be a task or a calendar item. Not only a task. > Currently the logic is that if one deliverable of a salesproject gets ordered, a project with a name correspondig to the salesproject is created and a task with a name corresponding to the deliverable. In o.o.invoices, there is a handler (/projects/) that allows you to create an invoice for multiple (closed) tasks. All that would have to be added would be to create a relatedto to the respective deliverable on invoice creation and this would be implemented > **Invoices:** > - We should be able to handle incoming invoices. They should be linked to a > project. They should be treaded as the others but a field that shows the > supplier instead of a customer. > - One supplier invoice can be linked to many different projects. (1 server > for one client. 1 workstation for another and so on. This part will be > tricky!!.) > - Can we export this a sie (www.sie.se i think this is only a swedish format) > or xbrl (a free and open standard www.xbrl.org this would be the most logical > choice) This would help bookkeeping alot. > Supplier invoices should be scanned and imported in some way. Batch mode or > single mode. Most probably using pdf's. This would make projects management > easier. Instant access to invoices linked to a project. > - One view would give a list of unhandled invoices with search fields to link > them to projects based on id's or names. And a field to input the amount that > that invoice should load the project. You should be able to enter several > projects with amounts. > > **Expenses:** > - Hour reports should contain milages, so that we can keep track on that cost > aswell. > - A definition on milages costs should be made somewhere aswell. > - A meeting in the calendar can also be an expense. > The list of tasks when creating a report should only display open or not > started tasks, not closed. > > **Directmarketing:** > - Responce from a campaign should/can this be linked to a sales project. So > that reports can contain such information aswell? > > > **Community/DBE:** > We should provide a DBE like functionality. Workflow should be able to work > between different OpenPSA systems. A first step should be to query other > systems for competence and send tasks between systems. This will probably be > after we have fixed the other stuff :) > _______________________________________________ > user mailing list > [email protected] > http://lists.midgard-project.org/mailman/listinfo/user _______________________________________________ user mailing list [email protected] http://lists.midgard-project.org/mailman/listinfo/user
