When I automated an item to created a few subitems, I want them to be dependent to one another. In another words: I have the subitems as steps. So one can only start if the other one is done. But those subitems are created only if the status is changed to X.
I cant make them dependent to each other in the automation bc they are not created yet.
Right?
Any other way to make it happen? Am I missing something?
You are absolutely correct, and this is an issue we have faced many times.
What we try to do is either utilize template boards if applicable to the use case ( because the dependencies there carry over) or use Make.com to create the tasks with the dependencies prebuilt ( let me know if you need any professional help with that!).
I know it’s a big issue, but unfortunately I do not think we are going to be able to natively do this with monday any time soon.
@GiannisKoukounas - In your previous reply (dated Feb 15), you said template boards would work, “because the dependencies there carry over”.
I created a subitem template by copying an existing collection of subitems. In that collection, there were dependencies in the subitems. These dependencies did NOT transfer over to the template, and when the template was applied to a new item, the dependencies did not appear.
How can I make dependencies become a part of a template, and from there work when applied to new items?
@GiannisKoukounas - I thought it might be helpful to provide more info on what I’m trying to do.
The dependencies are to help with status triggering to subsequent columns. Each subitem is a stage in a project. When a status is changed to “finished”, then it uses the dependency column to “drop down” to the next task in line, and trigger that status.
This is an important part of our automation sequence.
We developed an app called subitem automations that provides robust automation capabilities to subitems. Here’s an example of how it can be applied in this case →
Coming back to this question to see if anybody has been able to do this maybe in the workflows- it feels like this would work perfectly there but I was unable to access while building a workflow… TIA