Streamline work using Bundles

[Jan-Rienk]

@Chris_Pearson

so in effect, you could have 3 types of custom fields - 1 specific to a project/project template, 1 in the field library or 1 as part of a bundle.

@Chris_Pearson And the fourth ‘hybrid’ option of a custom field that is both a library field and added to bundles.

In that case access is managed at the field, not the bundle.

@Chris_Pearson

I must think about this over a cup of tea and a biscuit.

That sounds like a perfect idea.

[Chris_Pearson]

@Jan-Rienk

@Chris_Pearson And the fourth ‘hybrid’ option of a custom field that is both a library field and added to bundles.

In that case access is managed at the field, not the bundle.

Thanks @Jan-Rienk now there is a Global Field dashboard and Fields in Bundles I can work through the 4 scenarios, I feel a flowchart coming on.

[Jan-Rienk]

Edited article to add use cases by @Tiffany_Fung, @Richard_Sather, and @Chris_Pearson

[Jan-Rienk]

Edits:

• Updated “Generate bundle from project” “Bundle this project” since name/interface change
• Added alternative to section sync.

[Richard_Tasker]

in step 5 (Autochase) how did you get the dynamic @{assignee} to convert to

[Jan-Rienk]

Hey @Richard_Tasker,

Sure, that’s a variable in a rule

Find the + in the action’s menu on the right and you can insert them in various places.

PS: I updated article with reference to the feature.

[Richard_Tasker]

Thanks you. I am all set.

+ People > Assignee > Default