When I create a new item, I’ve set up an automation to add subtasks but I want to be able to assign a due date based on the parent due date and automatically connect the dependencies.
So automate:
add subitem x at 10 work days before parent due date
add subitem y at 7 work days before parent due date and set x as a dependency
add subitem z at 3 work days before parent due date and set y as a dependency
It seems silly that you can’t automate dates for subitem based on the parent item date but I can’t figure out how to automate a date to anything other than “today” or a specific unchanging date. I assume this is because it needs a date for the automation to function but you could add a condition that the parent date needs to be populated for the automation to run. I tried doing it with IF statements which kind of works but then you can’t display those dates in a calendar view and I can’t figure out how to set the IF statement to include everything that needs to be in there to make it really functional.
Setting dependencies is also time consuming since you have to search through every item. It would be great to be able to drag to connect them (like how you can parent layers in After Effects) instead of having to do a search every time or set a function where you can select a list and automatically create dependencies based on their order.
Up on this. I have an average routine workflow where 1 item = 1 project. And within that 1 project (item) are some tasks that I need to do. I just want the subitem due dates to update automatically when I set the due date for the parent project (item), and it’s so frustrating to do.
Any updates? This is a simple relative date assignment that some of your competitors have. Please add this as it takes my team hours to manually set due dates for subitems every quarter.
We developed an app that solves this exact problem of setting sub-tasks dates based on changes in its item’s date (basically a dependency item - subitem). You can also set different offsets for each subitem if needed.
See exmaple here -
I was looking at this app earlier today. I am trying to create a set of subitems when an item is created via automation (which I can do) that also has dependencies properly mapped (which I can’t). Would this app enable me to create a subitem template that includes properly mapped dependencies?
Each item represents a project that produces a specific type of deliverable. Each project has a certain set of tasks needed to complete it, which are the subitems. We can automate all of this to be created when a project requestor fills out a form.
What I am trying to solve for is the currently manual process of mapping dependencies. I’d like to either map the dependencies as the subitems are created based on logic that the automation dictates OR duplicate the template and create a new item when a form is submitted so that the dependencies already mapped are used.
Hi! The type of use case Alex Walton is describing has come up repeatedly for numerous users in our organization as well.
We need to be able to automatically create a set of subitems with pre-configured dependencies (the dependencies are between the subitems of the same parent item).
Parent Item
Subitem 1
Subitem 2
Subitem 3
Subitem 4
The subitems must happen in order, i.e. Subitem 4 is dependent on Subitem 3, which is dependent on Subitem 2, which is dependent on Subitem 1.
There isn’t a way to automate this natively. If your app can solve this, our org will consider adopting. (That being said, this organization has HIPAA data compliance requirements, so third-party apps have to be closely reviewed for security standards prior to installation.)
I also have the exact same use case. Parent item generates several subtasks depending on the project status. Subitem 4 is dependent on 3, 3 is dependent on 2, etc. Is there a way to not have to set these up manually and just have it be part of the automations?
@Fantasy-Media-Team Hmmm, none of those seem to work for my use case unfortunately. I tried setting up the automations above and none of them produced dependency information or linking. The Dependent On column is still empty when using any instance above.
I appreciate your work when it comes to filling this functionality gap, Fantasy Media team.
–
However, I’m extremely frustrated by Monday’s constant “well there’s an app for that” dismissal of customer needs for fundamental features (which are present in most comparable tools in the field, and which customers have come to expect.) Rather than actually enhancing their native platform, it seems they consider the existence of third-party apps that offer the desired functionality to be the ‘solution’, and the end of the conversation. That’s not a solution—especially for orgs with stringent data security policies. And when you consider the fact that almost all of these third-party solutions have independent licensing models (and therefore come with additional—often substantial—costs) it’s clear this approach is a recipe for discontent.
To any potential Monday customers, I offer this warning: when sales reps tell you “Yes, Monday can totally do [that thing you’re asking about]” they often actually mean ‘it can do it if you install this paid third-party app’. Beware.
