First of all, thanks so much for signing up for an account here on the Project Flow & Tracker site.

We are in pre-alpha now, so the interface still leaves a lot to be desired, and we are lacking important functionality (like Version Control connections, viewable and downloadable reports, etc.) but PFT is still usable now.

I notice that most of you "lose" your content due to failure to observe the following procedure, which is explained in the online context sensitive help (look for the "?" icon):

1. Create the project content type.

2. Go to the project page.

3. Click on the blue "Make Target" button so that you will have the opportunity of making the project the parent of the Role, Risk, Project Document, and Release and/or Iteration entries which should link to this top level.

4. After clicking "Make Target", the Link Target section will say "This node is the current target - when editing other nodes, you can associate them with this one."

5. In the Project Block on the upper right hand corner, click on Create Role. In the section entitled "This node is a child of the checked nodes (uncheck to remove, check to add)" select the "This node" checkbox. The sentence now reads "[project name] project involves [this node]. It is imperative to remember to select this checkbox! Then when you save your Role, you will see "This project involves [link to Role]. And when you are in the Role, you will see "This role is used in [name of project]".

6. Repeat this all down the workflow hierarchy (Project > Role > User Story > Task; Project > Release > Iteration > User story; Project > Feature > User Story ... or whatever you like :)     Then you will be able to drill down and zoom out, and really be able to see the forest for the trees.

I will make this easier and more automatic as soon as possible, and more importantly, I will include some graphical navigation for drilling down and zooming out.

The next improvement will be the ability to drill down from User story > Task > Commit via the Version Control API, so we will be able to complete the bi-directional traceability from the requirements to the code level!

Also, this whole website application will be released as an installation profile on drupal.org.

I am planning a few podcasts which will be made available here on the site.

Please continue with your valuable feedback at http://projectflowandtracker.com/contact .

Saludos,

Victor Kane