| 7 | | We could see if the Trac code can be reused here at all. |
| | 7 | This has so far been built in Vol & subsequently moved to Org, but the user-facing part will move into a project controller (whether the models follow is still up for debate). |
| | 8 | |
| | 9 | Requirements outstanding: |
| | 10 | * Project Task assigned to should show Title (& name) in .requires/.represent |
| | 11 | * Project Task assigned to should be 1->M component & link table should track %FTE |
| | 12 | * Dropdown of roles to assign to the project should by default be filtered to just those with spare capacity on these dates |
| | 13 | * This can be easily over-ridden by unticking this checkbox (same place as filter to just my organisation(s)/my office(s) |
| | 14 | * Onvalidation check should warn when roles are being over-committed (link to other project if readable) |
| | 15 | * Staff_Budget should be a 1-1 component link (like person/volunteer) Name? |
| | 16 | * Project_Beneficiary should be a component link |
| | 17 | * this then acts as DVR!? |
| | 18 | * Project_Donor should be a component link: Need different key joins. beware export loops, so for now define components in controllers only? (try it out) |
| | 19 | * either move organisation crud strings to model or else define other donor ones |
| | 20 | * Need to integrate project/position with budget_staff |
| | 21 | |
| | 22 | |
| | 23 | Alternatives: |
| | 24 | * Trac |
