I’d love to be able to remove a project from the Bundle, but KEEP the rules, fields, etc. from the Bundle. AND/OR I’d love to be able to Archive or Complete a project and stop the project from auto-updating when the bundle is updated.
Currently, when you remove a project from a bundle, it removes:
- Sections
- Custom Fields
- Rules
- Task Templates
But when you add a bundle to your work, it keeps all of the fields/sections/rules/task templates you originally had, plus adds the new ones from the Bundle.
Use case: I have a bundle for a set of projects and we create ~20 new ones added to the bundle each quarter, but when the project is complete or is archived, I no longer need it to update with the new changes to the bundle. However, I may want to still maintain some of the old rules/fields for reporting purposes.
Why does it bother you it does update? An archived project with new rules and no activity wouldn’t mind, would it?
I think it makes sense though, right now the bundle keeps growing and growing. Every new project is added, this will make the overview harder to navigate.
Also, updating completed and archived projects when a bundle is updated seems a waste of CPU time.
1 Like
@Bastien_Siebman - @Jan-Rienk is spot on. It’ shard to navigate and processing resources where they aren’t needed.
As I mentioned, the removing an old project from a bundle but maintaining its fields/rules is also a good option. I can foresee a world in which we want to put in new processes/rules but don’t need them to be applied to the old projects that are completed. In fact, applying to old/archived/completed projects could affect tasks that still exist on those projects.
1 Like