Rolling forward dependencies for monthly project

I am trying to make a project that recurs monthly, with multiple dependencies within the project. It’s simple enough to make the tasks roll forward monthly, but is there any way to make it so that the dependencies roll forward on a month to month basis? Or do I have to manually add the dependencies when each new month of tasks is generated? I will be making copies of this project 20+ times so that would be very difficult to keep updated.

Hello @Carter_Vogt and welcome to the Forum!

I would suggest creating a custom Project Template in this case. You can turn an existing project into a template, and your assignees, due dates, sections, custom fields, tasks and dependencies will be kept. To automate this process, you can also create a rule that will be triggered by the completion of the last task in the past project to launch a new project from the template.

The rule’s format could be something along the lines of:
Trigger: When the task completion status is changed, the task is completed
Condition: [this could be any way you can mark that one specific task differently than all others, like a different value of a custom field or a different section]
Action: Covert task to a project + from a template

If you prefer to create sections per month within the same project, you can duplicate sections. The dependencies within the duplicated section will also be copied. You will simply need to assign new due dates to the newly created tasks.

I hope this helps!

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.