554 | | [[FootNote]] |
555 | | ---- |
556 | | = Old design notes = |
557 | | |
558 | | (I'm reworking these into a better flow for the whole document.) |
559 | | |
560 | | == Component Data == |
561 | | |
562 | | Each Gantt chart component or feature requires data to support it. For Trac-based project management, this data is often in addition to the core ticket data. |
563 | | |
564 | | In general, we might expect to have multiple resources assigned to a task but if we use a Trac ticket as the basis for a task, we have only a single resource, the ticket owner. |
565 | | |
566 | | === Core Fields === |
567 | | |
568 | | Core ticket fields include relevant to project management include: |
569 | | |
570 | | * owner (who is working on it) |
571 | | * milestone (what milestone this ticket is part of) |
572 | | * status (new, assigned, ..., closed) |
573 | | * summary (short description) |
574 | | |
575 | | Core milestone fields relevant to project management include: |
576 | | |
577 | | * name |
578 | | * due (date and time) |
579 | | * completed (treated as a Boolean: open or closed) |
580 | | |
581 | | === Additional Data === |
582 | | |
583 | | For project management, we must have the following additional information about a task/ticket: |
584 | | |
585 | | * estimate (expected work required to complete task) |
586 | | * percent complete |
587 | | * dependencies |
588 | | * percent effort |
589 | | |
590 | | == What do we need in the user interface ? == |
591 | | |
592 | | A "chart these" button on a report page would be very nice. |
593 | | |
594 | | It would be nice to be able to create task dependencies graphically using the Gantt chart as a GUI or to change a milestone date by dragging it along the chart. |
595 | | |
596 | | == Reader Feed Back == |
| 554 | = Reader Feedback = |
609 | | === More Feed Back Here === |
| 567 | == More Feed Back Here == |
| 568 | |
| 569 | [[FootNote]] |
| 570 | ---- |
| 571 | = Old design notes = |
| 572 | |
| 573 | (I'm reworking these into a better flow for the whole document.) |
| 574 | |
| 575 | == Component Data == |
| 576 | |
| 577 | Each Gantt chart component or feature requires data to support it. For Trac-based project management, this data is often in addition to the core ticket data. |
| 578 | |
| 579 | In general, we might expect to have multiple resources assigned to a task but if we use a Trac ticket as the basis for a task, we have only a single resource, the ticket owner. |
| 580 | |
| 581 | === Core Fields === |
| 582 | |
| 583 | Core ticket fields include relevant to project management include: |
| 584 | |
| 585 | * owner (who is working on it) |
| 586 | * milestone (what milestone this ticket is part of) |
| 587 | * status (new, assigned, ..., closed) |
| 588 | * summary (short description) |
| 589 | |
| 590 | Core milestone fields relevant to project management include: |
| 591 | |
| 592 | * name |
| 593 | * due (date and time) |
| 594 | * completed (treated as a Boolean: open or closed) |
| 595 | |
| 596 | === Additional Data === |
| 597 | |
| 598 | For project management, we must have the following additional information about a task/ticket: |
| 599 | |
| 600 | * estimate (expected work required to complete task) |
| 601 | * percent complete |
| 602 | * dependencies |
| 603 | * percent effort |
| 604 | |
| 605 | == What do we need in the user interface ? == |
| 606 | |
| 607 | A "chart these" button on a report page would be very nice. |
| 608 | |
| 609 | It would be nice to be able to create task dependencies graphically using the Gantt chart as a GUI or to change a milestone date by dragging it along the chart. |
| 610 | |