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.
