Portfolio integration template needs to rename folder and resource planner

Feature requests
, ,
1

Description

Portfolio Integrations is an app available in the marketplace that provides templated automations specific to portfolio objects. One automation template is called “When an item is created create project form template”. When this automation creates a project from a template it can be configured to rename the project to a configured value. However, when you choose to include a resource planner with your project, your project is created under a folder along with a resource planner object. The project is renamed to the configured name, but the folder and the resource planner retain their generic names. The automation needs to be enhanced so the folder and resource planner are renamed consistently with the project item, otherwise manual effort is required to rename the folder and resource planner after the automation runs.

What are you trying to achieve

I want to eliminate the manual effort of renaming a folder and resource planner every time the Portfolio Integrations automation “When an item is created create project from template” creates a new project. I also want to ensure naming consistency within my portfolios and projects.

2

Hi @DavidDvorak

You’re calling out a real gap here, and you’re understanding the behavior correctly.

With the Portfolio Integrations app today, the automation only has control over the project object name itself. When a resource planner is included, monday treats the folder and the resource planner as separate objects that are created alongside the project, and the automation does not currently have the ability to rename those additional objects. That’s why you’re seeing the project renamed correctly while the folder and resource planner keep their default, generic names. Unfortunately, that part is expected behavior right now.

There isn’t a true native fix yet, but there are a couple of partial ways to reduce the manual effort.

One option is to standardize your templates so the default folder and resource planner names are as neutral or reusable as possible. That doesn’t solve the problem completely, but it minimizes the friction if renaming occasionally slips through.

If your naming convention is predictable, another workaround is to skip including the resource planner in the automation and instead add it after project creation using a consistent manual step. That sounds counterintuitive, but for some teams it’s actually faster than renaming multiple objects every time the automation runs.

For more advanced setups, some teams handle this via the monday API. It is technically possible to listen for project creation events and then programmatically rename the folder and resource planner to match the project name. That approach requires custom development and admin level access, but it is currently the only way to fully automate consistent naming across all related objects.

From a product standpoint, your request makes complete sense. If the automation can rename the project, it should also be able to rename any dependent objects it creates. This is a strong candidate for enhancement, especially for teams managing a large number of projects and portfolios.

I’d recommend submitting this as official feedback if you haven’t already, because it’s very aligned with how real portfolio workflows operate. If you want, the Monday Wizard team can also help you think through whether an API based solution or a lighter process adjustment makes the most sense for your setup in the meantime.

3

Thank you for the detailed response. You mention “submitting this as official feedback”. How do I do that? I posted this as a feature request, is that not “official”?

4

Hi David! Mia from monday.com :smiling_face:

You’re spot on - by posting this as a feature request, you’ve done exactly what’s needed. I’ve officially captured this in our feedback loop for the product team. Thank you for helping us make the platform better!

5

Yes it is. It becomes a feature request. Once they determine multiple users need a request and it gets added to their roadmap then they will add to development and will provide a solution to feature request if they see it will be beneficial to a lot of people. Usually thats how product development cycle works.