The document discusses the data model implementation for project management, focusing on entry types such as projects, milestones, and tasks. It outlines the relationships and associations between these entities, including metadata like due dates and priority. Additionally, it covers customization options using XML forms and features of the traction SDK to enhance task management processes.

1. PM Architecture Andy Keller Director of Engineering Dave Shepperton Senior Software Engineer

2. Two main parts Data model Implementation 2

3. Data Model: 3 entry types Projects Milestones Tasks

4. Data Model: Spaces vs. Projects In Traction 4.x, we referred to Spaces as Projects The term Project is now used for a set of Tasks and Milestones In the SDK and SDL: Project is still used for Space Goal is used for Project – to avoid confusion ;-)

5. Data model: Projects Normal Entry Title, Body, Author, Tags, Attachments, Comments, etc. Additional Metadata Due Date Owners Members Status Associated Entries Has Milestones Has Tasks

6. Data model: Milestones Normal Entry Title, Body, Author, Tags, Attachments, Comments, etc. Additional Metadata Due Date Status Associated Entries Has Tasks May belong to a Project

7. Data model: Tasks Normal Entry Title, Body, Author, Tags, Attachments, Comments, etc. Additional Metadata Due Date, Start Date Status, Priority Assignees Estimate, Duration Associated Entries May belong to a Project May be associated with a Milestone, which provides a default Due Date

8. Entry Labels: used for PM Task Project Milestone Milestones have Project Tasks have Project and Milestone

9. Data model: Task associations Task Task associated with a Milestone Task in a Project Task in a Project and Milestone

10. Data model: Relationships Tasks can belong to a project and assigned a milestone (optional) Milestones can belong to a project (optional) Tasks, milestones, and projects can all have a due date and other metadata

11. Implementation Indexes task metadata in a database Uses new features of the Traction SDK Custom entry types Entry decorators Entry labels XML Forms

12. JavaDB for the index Content is stored in Traction as Entries Title and description Labels Entry properties Indexed in the DB Simple SQL queries Sorting, totals, etc.

13. Pipeline Custom forms Content stored in the journal Event listener indexes metadata in database db.query tag to query the database db.entries tag turns query results into entries

14. XML Forms Covered this morning in customizing profiles 5 forms taskinline, taskitem, taskdialog milestone goal

15. XML Forms: triggering renders a form inline in the page creates a button to add or edit a form in a dialog fqid= attribute will trigger an edit

16. XML Forms: HTML rendering taskinline and taskdialog use HTML rendering offers more customization of layout, but still using XML controls

17. XML Forms: HTML rendering < gwt.rpc.form > < gwt.rpc.field > Turns an HTML block into a form, replacing fields. Replaced with a control from the schema.