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.
2 Likes
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
I haven’t seen any feedback on this specific request yet. I apologize if I missed one.
I am interested in a toggle to allow the engine to leave behind a static copy of sections/fields/automations when removing a project/project template from the bundle.
I love using the bundle to update five projects at once. We often have 3-6 active monthly project at any given time. However, I worry about a continually growing list of projects as we finish monthly projects within the bundle. I don’t need to updating 30+ projects every time I update the bundle - probably only the last rolling 10 projects at most.
As some of the projects come to a close, I would love to start dropping them off the bundle, but the one time I did this it was a mess as the bundle removed all the fields/sections/automations that came from the bundle. I couldn’t even recognize the project anymore! How can I archive a project and roll it off the bundle without it loosing its structure? Our sections/fields/automations are complicated, so I don’t have time to add them back in manually every time I want to graduate a project off the bundle. I don’t need it to update along with the bundle anymore, but I can’t drop it from the bundle until there is a way to leave an imprint of the bundle sections/fields/automations as it was at the time of removing the project from the bundle.
Hi @Anastasya_Raichart , good idea, I see how this would be useful.
Don’t forget to vote for your request, just like I did!
PS: I’ve moved this into an existing thread where votes are consolidated.
