More options for creating a subtask from blueprint in automations

Hi! Im working on setting up some subitems from a blueprint using automations, and the dates of these really need to be able to coincide with the parent task, or are otherwise useless.

Ideally, having all of the same options as when you launch a blueprint available here makes sense!

More discussion in the comments here.

Find more posts tagged with

Gathering votes

Status: Gathering votes

Comments

Juan Muttoni

Hello @Catherine Sneed, thank you for sharing this suggestion with us, it's definitely an interesting one and I have passed it on to your Product Development Team 👍

Catherine Sneed

Thanks Juan!

Erik Roberts

Same issue here, that's really the missing link for an effective solution. We're using automation to hand off completed brochures for publishing. Our rule creates subitems, assigns, and notifies team members for a handoff, but doesn't permit us to trigger a due date/task duration.

Juan Muttoni

Hello, @Erik Roberts, welcome to the Community! Thank you for chiming in, I've passed your feedback on to our Product Team 👍

We'll keep you updated in case there are any changes implemented to this feature. If you have any other questions, please let us know.

Also, I'd like to mention that you can check our New to Community forum to discover all the resources you can find in our Community 🙂

Brian Krause

Upvoting this. Every use case we have for automations involves creating tasks and projects from a blueprint. I was advised by support that when an item is created from a blueprint it inherits the due date from the blueprint, which can only be a static date - it cannot be dynamic. I can't think of a single use case where a user would want a blueprint, a template, to fire repeatedly over time, but to have all the tasks due on, for example, October 31st, 2024, every single time.

At present, we've had to leave due dates out of our blueprints, and when the automation fires, the first step is for someone on the team to manually follow up to set dates on the subtasks. Having to manually follow up on an automation severely limits the utility of the automation.

The workaround suggested by support was to not use automation, but to manually create our tasks from the blueprint.

Please add the ability to:

Set a dynamic date in a blueprint (e.g. "current date" or "x days from current date")

And/or allow an automation to set a dynamic date as above when creating a task from a blueprint.

Basudha Sakshyarika

That makes total sense, @Brian Krause! I can see how the ability to set a dynamic date in a blueprint will definitely be useful. I have forwarded your feedback to our product development team. 👍🏽

Louis Vermeulen

@Basudha Sakshyarika Any updates on this? Not having dynamic dates in blueprints makes them inefficient—we have to manually adjust dates every time tasks are created. A dynamic option would really streamline the process.

Shey MUSIC

Following up on this. Being able to use blueprints in Automations isn't really helpful if the dates don't adjust. It defeats the purpose of a blueprint entirely. This suggestion is 2 years old with no solution in sight. Is there a way to see the roadmap of what's coming? I find it pretty disheartening to see so many needed features sit in this forum for literally years without a meaningful update.

Rohan V

Hi @Louis Vermeulen and @Shey MUSIC 👋

Thank you both for reaching out and following up. I understand it can be disappointing when a feature you need isn’t available. We take upvotes into consideration to gauge the popularity of feature suggestions. At this time, there are no new updates to share, but please rest assured that we are passing all comments along to the Product Team for their visibility.

In the meantime, please consider upvoting the post above by clicking the “👍” symbol. To learn more about our Product Feedback guidelines, check out this detailed article. Thanks again!