Updated by George Britten
Your project may well be using a Work Breakdown Structure to organise tasks and set a consistent structure, even if WBS is not set as one of your required fields. A WBS can be created in app, or imported and then edited.
If you're an Editor looking to structure your project, you might want to check out our Packages article.
What is a WBS?
Importing your WBS
Your WBS can be imported straight from your master schedule, whether you're building that out in P6, Asta, Microsoft Project...
Setting this process up properly will also automatically assign parts of the WBS to the relevant activities, saving the whole team time!
Creating & Updating Your WBS
You can access your project's WBS using the sidebar and heading to the 'Structure' page under 'Project Assets'.
From here, Project Admins can create, re-order, re-structure and re-name parts of the WBS by selecting a row and using the arrow keys to indent, outdent or move sections around.
When adding and editing a WBS, your WBS Code is the unique identifier and will determine position in the overall structure. Your WBS Path is the more detailed breakdown and is specific and unique, for example 220.127.116.11.
Creating a new branch in your WBS automatically makes a new child, and begins a new path. Equally, moving a branch in your WBS structure will move all the children as well.
Once you're happy with your WBS, it's quick and easy to assign specific WBS sections to tasks in your plan.
Deleting Parts of the WBS
Deleting parts of your WBS will remove these from tasks too, leaving the WBS column blank for those activities.
Unlike other project assets, elements of your WBS cannot be archived. Deleting these structural components is irreversible, so make sure you're certain before you hit the button!