Hello! I’m new to the world of rules and could use your help! I’ve created a set of rules to when a task is moved to a section within the project, a task with subtasks autopopulates. I’d like the rule to set relative due dates based on the parent task’s due date. Is this possible? Here’s how I currently have the rule set.
1 Like
Hi @AgentWell , welcome to the forum 
It looks like you figured it out already! See the summary, it describes the result you want to achieve, right?
Btw, I also noticed your Section names are matching your Podcast status field and thus you are having to build them into your rules to keep them in sync. Instead, you may want to consider this approach:
@Richard_Sather I figured out the sections with task population, but not the cause issue of a relative due date. When I add a new task to this project, and I set that parent task’s due date, I’d like the subtasks to autopopulate due dates. Here’s the due date flow I’m trying to achieve:
Podcast Episode (Parent Task)- Due Date: X
Prep Tasks (Substasks set when the task migrates to that section)- Start Date: 21 Days before Due Date X; Due Date: 14 Days before Due Date X
1 Like
Hi @AgentWell , sorry, I’m not following what is the issue you are facing. Your rule appears to be correct, based on what you are describing:
- Create a task, set the due date
- Move the task into a section → rule will create subtasks
- Subtasks will be created with start & due dates based on/relative to parent task’s due date
Can you describe what is NOT working as expected?
I assume there is a section where the tasks are initially created and a due date is set before adding them to a particular section, correct?
You could improve your rule by adding an AND condition to check if due date is not empty, in addition to your existing Check if section is.. condition.
And you could also add a 2nd When.. Rule is run manually so that you can manually create subtasks for testing purposes or when you want to create them on the spot.
I understand using Groups instead of using Sections is not related - it was just a side note.
The rule is not generating the start and due dates even though the parent task due date is set and the due date is further out than 21 days.
1 Like
Hi, @AgentWell .
I tried it too. When I moved to the section, a subtask was created and a due date was set.
In your case, what is the activity status of the problematic task?
Thinking about it again, I created a subtask and set a due date, but it seems there is no action to set a start date.
The rule with the start date set looks like this.
|
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.