Bundles and templates
Asana's bundle and template hierarchy is widely reported as confusing — applying a bundle to a project that already used it creates duplicate sections, rules and fields users then clean up by hand.
Ce que les utilisateurs disent vraiment
✕Generating a bundle from a project and re-applying it creates duplicate sections, rules, task templates and custom fields users have to remove manually.
Source : Asana Forum, bundle generation creates duplicates ↗✕When a project is saved as a template, its bundle is not included, forcing manual re-add which then creates the same duplicate sections and rules.
Source : Asana Forum, bundles excluded from saved templates ↗✕Task templates created inside a bundle do not always show up on the projects tied to that bundle, breaking the promised inheritance.
Source : Asana Forum, task template not appearing from bundle ↗
Templates in a tailored build are versioned rows in Postgres with an `applies_to` relation, applied idempotently — re-running an apply diffs against current state and only adds what's missing. Bundles are just composable template fragments referenced by id, so updating a bundle updates every project using it without duplication, and saving a project as a template captures its bundle references by default.