Time Calculation

Francisco, are you understanding the concept that you need to create a new table to hold the start and end times of each stage?  This will be a child table to the projects table.  So when a stage changes a child Stage History gets created by the Pipeline, so we know the start time of the Stage.  But before the creation of the Stage History record, the pipeline will close off (set the end time) of any previously created Stage Histories which are still running their clock (of course there should only be one).  If you were to look at a Project there will be an embedded report on the form of all the Stage History records.

Then you will use a summary field on the Relationship to summarize the total duration of the stage histories which have the same Stage as the current Project Stage, but there should only be one child to summarize for each stage unless the project moves "backwards" to a previous Stage in the Kanban.