Settings
Importing and Exporting Bundles
A bundle is a packaged snapshot of a Spruce project's configuration: templates, views, actions, and other non-artifact content. Bundles let you reuse a project's setup without copying the project itself.
What's in a bundle
| Content | Included? |
|---|---|
| Templates | yes |
| Views | yes |
| Actions | yes |
Project config (project.yaml subset) | yes (focus bar filter, default view) |
| Artifacts | optional (opt-in at export time, opt-in to include at import time) |
| Comments | no |
| Linked code repos | no |
Bundles are mostly portable setup. Artifacts are off by default but you can opt in when you want a populated starter, e.g. a "getting started" bundle that bootstraps a new project with onboarding tasks.
Exporting a bundle
From the current project, go to Settings → Import / Export → Export bundle. Pick which content to include; default is all templates, views, and actions. Give the bundle a name and Spruce writes a .zip file with a manifest (bundle.yaml) at the root.
Bundle export dialog with content checkboxes and a name field
Importing a bundle
From any project, go to Settings → Import / Export → Import bundle and pick a .zip file. Spruce shows a preview:
- New templates / views / actions that will be added.
- Existing ones that would be overwritten.
- Conflicts per file.
Choose how to handle conflicts per item (skip, overwrite, or rename). Apply.
Bundle import dialog with content checkboxes and conflict handling
Common uses
- Team templates: a design org defines a shared
rfctemplate and exports a bundle so every team can import it. - Project bootstrapping: a new project imports your org's standard bundle to get consistent templates and views from day one.
- Reset to defaults: Spruce ships a "base" bundle with the default templates and views; import it to restore defaults on a messy project.
The base bundle
Every Spruce project starts from the built-in base bundle: the feature, task, bug, chore, and memo templates plus the built-in views. It's also available as an importable bundle if you want to reset a project.
Resetting from the Packs section
To reset a project's templates and views back to the base bundle, head to Settings → Packs (at the bottom of the project settings sidebar). The Packs section lists every bundle you've imported into the project, including the base bundle, with a Reinstall action that overwrites the project's templates/ and views/ from the bundle.
This is the easiest path for "I've made a mess of my templates, give me the defaults back". No need to find the base-bundle .zip and run it through the Import flow.
Related
- Editing Built-in Templates — what gets exported.
- Views — the view config bundles ship.
- Actions — action definitions bundles ship.