ASK: Bundles applied to a portfolio should be applied to all future projects that are added to the portfolio, not just to the projects that are already in the portfolio at the time of launch.
USE CASE: We’re a SaaS org with three distinct divisions, let’s say ABC, DEF, and GHI. I’m creating project templates for use within the ABC division, inside an ABC portfolio, but the DEF division wants to use them too. Inside the templates are fields setting the division to ABC, because I made these for ABC, and I want rules in other projects to fire on the projects created from the templates based on it being in the ABC division (assignees, custom fields, etc.).
DEF doesn’t want to recreate the templates, fair enough, but can’t have the tasks auto assigning to ABC division. I thought I found the solution in a Bundle that sets the Division to ABC, another bundle that sets the Division to DEF, and apply the bundles to the ABC and DEF portfolios respectively. I created a new project from a template in the ABC portfolio, watched the rules fire, and behold! the ABC division bundle rule did NOT fire, and I think it should.
Maybe as a deselectable option upon adding it, should there be a use-case to not want this applied to all future projects.
Either way, at least an option to remove it later, as you want to be able to stop it without having to replace the portfolio.
1 Like
Absolutely! We get all the options when duplicating tasks or projects, what to do, what to keep, etc., the same should appear when working with a bundle.
1 Like
Upvoted! I would really benefit from this.
I am in a similar situation to OP, and it’s forcing me to maintain multiple project templates where the only difference is 1 bundle that is specific to each team. I would love to have either a rule or a setting that auto-applies the relevant bundle when a project is added to the relevant portfolio.
Until that’s available, I’ll likely shift to a workaround where I have 1 centralised template for all teams, and a task in the project template that prompts me to manually apply the correct bundle upon project creation by a team member. It’s not ideal and obviously has risk in time-delay in me seeing the request/manually adding the bundle - but seems like less effort than maintaining multiple templates whenever there is a non-bundled change.
(For what it’s worth, I control as much as possible in the project templates via Bundles, but there are some components, such as tasks in the actual body of the project template, that I can’t bundle, so I need to manually update multiple templates anytime those non-bundled elements require a change).
