Forum Discussion
Okay, perfect.
By saying different stages I mean like the different parts of my process, the Project needs to pass through all of them in order to be completed, each "Stage" has their tasks and I thought that the dependencies created with predecessors was in de task level and not in the "Stage level".
The image that you put its okay, that is what I want to do.
In addition to this, the tasks of the following stage are created only when the project enters that stage, with a pipelin, thats why I thought that it coudldnt be done with predecessors.
thanks!
------------------------------
Francisco Ojeda
------------------------------
Francisco, if you have a setup where one Project has many Tasks and the Tasks know which Stage they are for, then you can make a summary field for the total number of open tasks for where the Task Stage equals the current Project Stage. Then you can use data table rules in advanced settings for the table to create and error message such as
IF([# open tasks for current stage] > 0, "Sorry, but you must complete the Stage Tasks before you can move the project in the Kanban")
Then what will happen in that the user will drag the card but it will not stick and will revert back to where it was and display the warning message.
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------
- FranciscoOjeda2 years agoQrew Trainee
Thank you very much!
I will try with this.
------------------------------
Francisco Ojeda
------------------------------- FranciscoOjeda2 years agoQrew Trainee
Here I am trying to create the Summary field, I dont know how to set it to "equals the current Project Stage."
------------------------------
Francisco Ojeda
------------------------------- MarkShnier__You2 years agoQrew Legend
First look up the current project stage down to the Stage history table.
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------